New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@Kris,
What are you even talking about, do you even know? Its easy to understand. Its like a breaker in a house. If you turn one off directly related to the kitchen, then the kitchen stays off but the rest of the house still works.
Im pretty sure that is what happened here, only a segment of the DC was effected not all. I do not know all the details, but your over reacting and saying some things that are not warranted. Were you a client of ours before?
ColoCrossing doesnt need a spokes person here. All they need to do is talk to their direct clients and owe nothing to you or anyone else that is an end client. For now on I just wont even join any discussion involving them as you always try and backfire it on me.
Back to vacation. Deuces.
@Kris
At least right now there's no cogent - everything inbound is via Telia.
Also from http://www.cogentco.com/en/network/looking-glass we can see cogent isn't currently seeing this as a path
BGP routing table entry for 192.210.232.0/22, version 127245170 Paths: (1 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 1299 36352 66.28.1.199 (metric 101012) from 154.54.66.76 (154.54.66.76) Origin IGP, metric 4294967294, localpref 100, valid, internal, best Community: 174:10031 174:20666 174:21000 174:22013 Originator: 66.28.1.199, Cluster list: 154.54.66.76, 66.28.1.69, 66.28.1.89, 66.28.1.197If it happens again you can use the looking glass to test/confirm.
Agreed. The "normal" situation seems to have been fixed. No more Cogent.
Yup, I own a linux VPS review site.
The last time I spoke with Jon about LET, he had no intentions in joining any discussions at all.
On the other side, I've noticed some of my servers routing through cogent a couple of days ago as well.
@Alex_LiquidHost,
Are you seeing the whole route like that over Cogent? That was a weird route.
I am unclear where/how Cogent would be handling the full transit route since not directly peered.
I haven't seen Cogent show up yet. Although, I wouldn't mind seeing it to/from Vegas somehow.
Very true, it is a nice datacenter. Just kinda irks me that a lot of people openly advertise it as a "downtown/metro" datacenter when it's not close. But I'm sure the bandwidth is backhauled to the city. Would only add a few ms at most.
What in the heck is going on with CC's network in Buffalo?
I saw Cogent in my routes just a bit ago from Fiberhub in Vegas:
4: te0-3-0-0.ccr22.lax01.atlas.cogentco.com 7.857ms asymm 5
5: te0-0-0-5.mpd22.iah01.atlas.cogentco.com 44.000ms asymm 6
6: te0-0-0-1.ccr21.dfw01.atlas.cogentco.com 49.286ms asymm 7
7: te0-2-0-6.ccr21.mci01.atlas.cogentco.com 59.424ms asymm 8
8: te0-7-0-33.mpd21.ord01.atlas.cogentco.com 71.560ms asymm 9
9: no reply
10: no reply
11: 38.122.36.46 85.525ms asymm 12
12: host.colocrossing.com 84.165ms asymm 13
13: host.colocrossing.com 83.734ms asymm 14
Seems to be some flip flapping going on today...
We had a few minutes outage, received the same explanation. Didn't happen to all the servers.
It appears rows of racks went down. Not all.
Did not receive any email about any upgrades.
Was that outage the one earlier today @concerto49 or a second event today?
Weird.
BuyVM LV -> Normal CC Buffalo - over Cogent (new?)
BuyVM LV -> BuyVM Buffalo - over Telia (need to announce at the ASN?)
No clue what's going on.
@pubcrawler. Same event as everyone else I assume. No new outages since.
Something weird going on.
Tested from Vegas (Fiberhub) to Buffalo. Here's which route they took:
StormVZ = Telia
DotVPS = Telia
CloudShards = Cogent
EndofReality = Cogent
SpotVPS = Cogent
ChicagoVPS = Cogent
BuyVM = Telia
Fragnet = Cogent
URPad = Cogent
HudsonValleyHost = Cogent
IPXCore = Cogent
It's possible Alex never sent our LOA to Cogent so we don't take cogent.
Given FH has cogent you should really take cogent all the way since it'd be the shortest path.
The only reason it wouldn't is if Alex is either filtering those subnets to cogent, hasn't added those subnets to cogents prefix list (LOA required) or maybe FH is doing some optimizing for it.
Honestly, the FH route optimizing should be seeing cogent routes as the best way to go.
Francisco
Agree about the Cogent from Fiberhub. Cuts 20ms latency off --- well would --- but still on Telia.
Yep, that's the case for us.
We aren't on Cogents prefix list so we get handed off to Telia before we continue onwards.
Francisco
To add more to it, it looks like, at least for us, Level3 is removed from the blend.
A trace on http://lg.level3.net shows us always handing off to telia.
Not a huge deal if they removed L3 from Buffalo, but I'll have to poke them to get us on Cogents prefix list.
Francisco
"Brand New Buffalo NY Datacenter Opens! ColoCrossing is proud to announce the opening of our second NY-based datacenter. The new facility, located in downtown Buffalo, NY provides users with excellent routing and latency, with extremely competitive rates thanks to the areas robust hydro-power generation. Connectivity is Level3 and Centurylink. No Gogent and No HE bandwidth."
Then changed to L3 + CenturyLink.
Now changed to Cogent + Telia?
So much for that No "Gogent" bandwidth ehh?
Did they drop Level3 from providers? Appears so, L3 dumps off to Telia every time:
1 ae-5-5.ebr2.SanJose1.Level3.net (4.69.134.38) 404 msec 4 msec 400 msec
2 ae-92-92.csw4.SanJose1.Level3.net (4.69.153.30) 352 msec
ae-62-62.csw1.SanJose1.Level3.net (4.69.153.18) 4 msec 396 msec
3 ae-4-90.edge2.SanJose3.Level3.net (4.69.152.209) 336 msec 4 msec
ae-1-60.edge2.SanJose3.Level3.net (4.69.152.17) 12 msec
4 sjo-bb1-link.telia.net (213.248.98.29) [AS1299 {TELIANET}] 200 msec 4 msec 0 msec
5 nyk-bb1-link.telia.net (80.91.252.152) [AS1299 {TELIANET}] 72 msec 72 msec 72 msec
6 buf-b1-link.telia.net (80.91.246.36) [AS1299 {TELIANET}] 80 msec 84 msec 80 msec
7 giglinx-ic-155660-buf-b1.c.telia.net (213.248.96.42) [AS1299 {TELIANET}] 84 msec 84 msec 80 msec
1 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 8 msec 8 msec 12 msec
2 ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) 8 msec
ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 8 msec
ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) 8 msec
3 ae-3-80.edge2.Dallas3.Level3.net (4.69.145.140) 12 msec 8 msec
ae-1-60.edge2.Dallas3.Level3.net (4.69.145.12) 8 msec
4 4.68.70.58 8 msec 68 msec 20 msec
5 nyk-bb1-link.telia.net (213.155.130.64) [AS1299 {TELIANET}] 56 msec 48 msec 48 msec
6 buf-b1-link.telia.net (80.91.246.36) [AS1299 {TELIANET}] 60 msec 60 msec 56 msec
7 giglinx-ic-155660-buf-b1.c.telia.net (213.248.96.42) [AS1299 {TELIANET}] 56 msec 60 msec 56 msec
1 ae-1-60.edge1.NewYork1.Level3.net (4.69.155.14) 0 msec
ae-2-70.edge1.NewYork1.Level3.net (4.69.155.78) 0 msec
ae-4-90.edge1.NewYork1.Level3.net (4.69.155.206) 0 msec
2 telia-level3-ge.newyork1.Level3.net (4.68.63.214) 0 msec 0 msec
nyk-b5-link.telia.net (213.248.90.125) [AS1299 {TELIANET}] 0 msec
3 nyk-bb1-link.telia.net (213.155.135.18) [AS1299 {TELIANET}] 60 msec 120 msec 32 msec
4 buf-b1-link.telia.net (80.91.246.36) [AS1299 {TELIANET}] 12 msec 12 msec 8 msec
5 giglinx-ic-155660-buf-b1.c.telia.net (213.248.96.42) [AS1299 {TELIANET}] 16 msec 12 msec 8 msec
These are depressing developments. From South Bend, IN:
Almost seems that Tinet has preference of route, however if your upstream has Cogent it goes that route.
L3 I haven't seen any which way.
I'm seeing outbound L3 when going to L3 locations.
I actually have cogent in my outbound routes when going to FH but i'm a little confused about it all.
Francisco
Oh, the traceroutes are real fun now.
I recommend trying some yourselves from Buffalo...
This is to Kansas City (Wholesale):
2: 10.8.0.201 6.311ms asymm 3
3: buf-b1-link.telia.net 0.590ms asymm 5
4: nyk-bb1-link.telia.net 9.837ms asymm 6
5: nyk-b6-link.telia.net 10.114ms asymm 6
6: te0-0-0-0.mpd22.jfk02.atlas.cogentco.com 10.958ms asymm 8
7: 10gigabitethernet8-3.core1.chi1.he.net 21.256ms asymm 8
8: nyk-b5-link.telia.net 10.544ms asymm 6
9: 10gigabitethernet1-1.core1.mci2.he.net 40.427ms
10: hurricane-ic-138361-nyk-b6.c.telia.net 11.727ms asymm 7
11: 192.81.xxx 31.839ms reached
Someone want to explain that route to me
?
Telia to Cogent to HE to Telia to HE...
And looks like:
Buffalo --> NYC --> Chicago --> New York --> ???
What the.... that's strange
Hey I don't make these routes up @KernelSanders... It's CC's special sauce at work here.
Comcast routing is getting weirder. Went from only Telia this morning to now Tata being in the mix.
Now Denver, CO -> Palo Alto, CA (TATA) -> San Jose, CA (Telia) -> Buffalo.
100 ms+ is a little much for Denver to NY when just over half that to NJ, NY and even FL.
Hoping someone at CC puts down the nitrous.
Seconding this, from CA:
Ouch on those end times. This is the crap network/crap routing I moan about regularly on US coast-to-coast.
Level3 from Seattle to Buffalo, 68ms ping. Route goes down to Denver and then Chicago:
1 ae-1-51.edge1.Seattle3.Level3.net (4.69.147.138) 0 msec
ae-2-52.edge1.Seattle3.Level3.net (4.69.147.170) 0 msec
ae-1-51.edge1.Seattle3.Level3.net (4.69.147.138) 0 msec
2 sea-b1-link.telia.net (80.239.128.197) [AS1299 {TELIANET}] 0 msec 0 msec 0 msec
3 den-b1-link.telia.net (213.155.134.208) [AS1299 {TELIANET}] 28 msec 28 msec 28 msec
4 chi-bb1-link.telia.net (213.155.130.136) [AS1299 {TELIANET}] 52 msec
chi-bb1-link.telia.net (213.155.133.172) [AS1299 {TELIANET}] 52 msec 56 msec
5 cle-b1-link.telia.net (80.91.246.32) [AS1299 {TELIANET}] 60 msec 60 msec 60 msec
6 buf-b1-link.telia.net (80.91.246.35) [AS1299 {TELIANET}] 76 msec 72 msec 76 msec
7 giglinx-ic-155660-buf-b1.c.telia.net (213.248.96.42) [AS1299 {TELIANET}] 76 msec 72 msec 76 msec
This is much better than other Denver originated traffic on Comcast and heading to Cali to Tata and back over.
Comcast <-> Cogent is saturated in all 4 peering spots. The saturation exists on the Comcast side of the links and has been ongoing for a bit of time now. That’s probably why CC has you on Telia despite the less ideal physical route. This was being discussed recently on nanog.
Comcast takes Cogent to CloudShards:
So Telia has a PoP inaccessible by these routes in Denver?
Wondering why I go to Palo Alto, CA through Tata to get to Telia, if Telia's in Denver?