...
| Code Block |
|---|
traceroute to mbl-99-50-204.dsl.net.pk (203.99.50.204): 1-30 hops, 38 byte packets 1rtrg-nethub.slac.stanford.edu (134.79.19.1) 0.451 ms (ttl=255) 2rtr-core1-p2p-servcore1.slac.stanford.edu (134.79.255.25) 0.318 ms (ttl=254) 3rtr-dmz1-ger.slac.stanford.edu (134.79.135.15) 0.405 ms (ttl=252\!) 4192.68.191.146 (192.68.191.146) 0.440 ms (ttl=250\!) 5slacmr1-slacrt4.es.net (134.55.209.93) 0.409 ms (ttl=250\!) 6snv2mr1-slacmr1.es.net (134.55.217.2) 0.826 ms (ttl=249\!) 7snv1mr1-snv2mr1.es.net (134.55.217.5) 0.793 ms (ttl=248\!) 8snvcr1-snv1mr1.es.net (134.55.218.21) 0.925 ms (ttl=246\!) 9paix-pa-snv.es.net (134.55.208.205) 52.1 ms (ttl=245\!) 10g1-0-0.plapx-ar1.ix.singtel.com (198.32.176.50) 102 ms (ttl=244\!) 11203.208.168.133 (203.208.168.133) 94.4 ms (ttl=243\!) 12p1-0.sngtp-cr3.ix.singtel.com (203.208.182.129) 321 ms (ttl=243\!) 13203.208.182.157 (203.208.182.157) 306 ms (ttl=242\!) 14203.208.149.218 (203.208.149.218) 319 ms (ttl=241\!) 15203.208.149.105 (203.208.149.105) 385 ms (ttl=239\!) 16203.208.149.109 (203.208.149.109) 327 ms (ttl=238\!) 17203.208.147.238 (203.208.147.238) 287 ms (ttl=236\!) 18203.208.147.238 (203.208.147.238) 306 ms (ttl=236\!) 19pos1-0.rwp44gsrc2.pie.net.pk (202.125.159.21) 319 ms (ttl=236\!) 20ge-st.nayatel.pk (58.65.166.249) 328 ms (ttl=233\!) 2158-65-175-218.nayatel.pk (58.65.175.218) 313 ms (ttl=232\!) 2258-65-175-218.nayatel.pk (58.65.175.218) 317 ms (ttl=232\!) 23ge-0-1-bras1.dsl.net.pk (203.82.48.162) 334 ms (ttl=231\!) 24ge-st.nayatel.pk (58.65.166.249) 325 ms (ttl=233\!) 2558-65-175-222.nayatel.pk (58.65.175.222) 330 ms (ttl=232\!) 26ge-0-1-bras1.dsl.net.pk (203.82.48.162) 322 ms (ttl=231\!) 27mbl-82-56-95.dsl.net.pk (203.82.56.95) 371 ms (ttl=39\!) 28mbl-99-50-204.dsl.net.pk (203.99.50.204) 369 ms (ttl=38\!) |
Qaid-e-Azam University
PingER data shows that the link to Qaid-e-Azam university is heavily congested. The wave of congestion starts about 9:00 am in the morning and continues to about - pm in the evening.
Qaid-e-Azam University is connected through PERN and its ISP is NTC. The traceroute results (taken on 28th Feb 11:00 am from NIIT) showed that the link from PIE (Pakistan Internet Exchange) to PERN was congested.
...