As Charles Dye said earlier (I think) UNM blocks ICMP (Internet Control Message Protocol) which both ping and tracert use. Tracert, however, might show if there are particularly long response times, or lost packets along the way to UNM. I see a big jump in response times at the last couple hops before UNM.
Code:
v:\> tracert prospero.unm.edu
Tracing route to prospero.unm.edu [129.24.38.32]
over a maximum of 30 hops:
1 7 ms 6 ms 7 ms 142.254.212.205
2 25 ms 21 ms 22 ms tge0-0-1.syrcnysl02h.northeast.rr.com [24.24.16.13]
3 9 ms 9 ms 9 ms agg35.esyrnydr02r.northeast.rr.com [24.58.46.178]
4 19 ms 15 ms 16 ms be27.albynyyf01r.northeast.rr.com [24.58.32.80]
5 25 ms 23 ms 23 ms bu-ether46.nycmny837aw-bcr00.tbone.rr.com [107.14.19.102]
6 23 ms 28 ms 27 ms bu-ether11.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.26]
7 23 ms 23 ms 21 ms 0.ae1.pr0.nyc30.tbone.rr.com [66.109.6.161]
8 22 ms 21 ms 23 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 65 ms 65 ms 67 ms ae-21-52.car1.Denver1.Level3.net [4.69.147.99]
10 65 ms 65 ms 66 ms ae-21-52.car1.Denver1.Level3.net [4.69.147.99]
11 715 ms 388 ms 675 ms CENIC.car1.Denver1.Level3.net [4.30.24.58]
12 180 ms 395 ms 256 ms 208.77.76.149
13 * * * Request timed out.
Pinging one of those hosts ... I didn't see any lost packets.
Code:
v:\> ping -t 4.30.24.58
Pinging 4.30.24.58 with 32 bytes of data:
Reply from 4.30.24.58: bytes=32 time=86ms TTL=242
Reply from 4.30.24.58: bytes=32 time=88ms TTL=242
Reply from 4.30.24.58: bytes=32 time=374ms TTL=242
Reply from 4.30.24.58: bytes=32 time=353ms TTL=242
Reply from 4.30.24.58: bytes=32 time=349ms TTL=242
Reply from 4.30.24.58: bytes=32 time=340ms TTL=242
Reply from 4.30.24.58: bytes=32 time=409ms TTL=242
Reply from 4.30.24.58: bytes=32 time=86ms TTL=242
Reply from 4.30.24.58: bytes=32 time=311ms TTL=242
Reply from 4.30.24.58: bytes=32 time=592ms TTL=242
Reply from 4.30.24.58: bytes=32 time=303ms TTL=242
Reply from 4.30.24.58: bytes=32 time=534ms TTL=242
Reply from 4.30.24.58: bytes=32 time=112ms TTL=242
Reply from 4.30.24.58: bytes=32 time=543ms TTL=242
Reply from 4.30.24.58: bytes=32 time=618ms TTL=242
Reply from 4.30.24.58: bytes=32 time=264ms TTL=242
Reply from 4.30.24.58: bytes=32 time=493ms TTL=242
Reply from 4.30.24.58: bytes=32 time=171ms TTL=242
Reply from 4.30.24.58: bytes=32 time=378ms TTL=242
Reply from 4.30.24.58: bytes=32 time=417ms TTL=242
Reply from 4.30.24.58: bytes=32 time=384ms TTL=242
Reply from 4.30.24.58: bytes=32 time=586ms TTL=242
Reply from 4.30.24.58: bytes=32 time=143ms TTL=242
Reply from 4.30.24.58: bytes=32 time=504ms TTL=242