Web Hosting Talk







View Full Version : Which Backbones is Managed.com Really Using?


a-m
06-21-2004, 07:47 AM
Doing traces & tests recently to my server I have gotten Broadwing, AboveNet & now UUNET.

1 fast-3-0-1.mgl-7206.jkt.cbn.net.id (202.158.3.1) 297.115 ms 0.706 ms 0.592 ms
2 ip127-33 (202.158.127.33) 5.258 ms 4.473 ms 12.064 ms
3 ip127-65 (202.158.127.65) 26.295 ms 1.135 ms 0.538 ms
4 gw1-en-cbn.palapanet.com (202.93.46.129) 2.470 ms 2.357 ms 3.212 ms
5 gw-en-kppti.palapanet.com (202.93.46.134) 2.810 ms 2.684 ms 2.415 ms
6 500.POS2-1.IG2.SAC1.ALTER.NET (157.130.210.217) 186.824 ms 219.587 ms 188.396 ms
7 0.so-0-0-0.XR2.SAC1.ALTER.NET (152.63.54.118) 187.265 ms 187.392 ms 188.235 ms
8 0.so-0-0-0.XL2.SAC1.ALTER.NET (152.63.54.1) 189.532 ms 187.755 ms 187.890 ms
9 0.so-7-0-0.XL2.SJC1.ALTER.NET (152.63.55.133) 190.964 ms 192.202 ms 190.968 ms
10 POS1-0.XR2.SJC1.ALTER.NET (152.63.55.125) 191.496 ms 192.918 ms 190.101 ms
11 192.ATM7-0.GW3.SJC1.ALTER.NET (152.63.49.25) 191.347 ms 190.440 ms 192.294 ms
12 bungi-gw.customer.alter.net (157.130.59.54) 190.980 ms 192.687 ms 191.857 ms
13 66.79.175.17 (66.79.175.17) 192.049 ms 192.839 ms 276.002 ms
14 66.79.175.2 (66.79.175.2) 193.357 ms 191.100 ms 193.447 ms
15 66.79.161.10 (66.79.161.10) 192.386 ms 190.784 ms 191.479ms



anyone have any info? or can shed some light?

s2software
06-21-2004, 09:26 AM
When I do a traceroute from the Netherlands it goes through Cogent first, the through isc.org (???) and then a broadwing hop followed by the Managed.com core router.

tehtech
06-21-2004, 09:49 AM
AboveNET, Bungi, Layer42, XO.

Joshua
06-21-2004, 10:11 AM
Originally posted by tehtech
AboveNET, Bungi, Layer42, XO. If they have Layer42, it's only for a backup line at this point, and is not being used for incoming or outgoing. Their current mix is AssertiveNetworks (which consists of mostly AboveNet, Layer42, and Bungi on traces), Bungi directly, and XO directly. The way they have Bungi setup is very odd, as if I do an outgoing trace from Managed.com to Bungi.net, it goes over their direct line, whereas if I trace from Managed.com to 157.130.59.54 (Bungi's direct connection with UUNet, before it hits Managed.com), the trace goes out over AssertiveNetworks, then to Bungi. By the looks of the network outages forum, they still don't know how to add a bandwidth provider to the mix without causing issues for at least 50% of the network - It looks like they took down XO first, turned up Bungi, and put XO back on after adding Bungi with XO didn't work...

-Josh

tehtech
06-21-2004, 10:51 AM
Hmm. I could lend them one of my BGP books? :D

sirius
06-21-2004, 12:19 PM
Originally posted by tehtech
Hmm. I could lend them one of my BGP books? :D

That was my exact reply earlier, but I decided to delete it... :rofl:

Sirius