Level3 had an issue with one of their core routers in Los Angeles last night(7pm Pacific) and early this morning(1am Pacific). Last update to my trouble ticket had the issue still being reviewed by engineering, but that a core router was dropping packets.
Level3 had an issue with one of their core routers in Los Angeles last
night(7pm Pacific) and early this morning(1am Pacific). Last update to my
trouble ticket had the issue still being reviewed by engineering, but that
a core router was dropping packets.
I have seen this several times with level3. They confirm packets are
dropping and sevice is degraded yet they refuse to take tactical corrective
action for hours and hours.
Wow .... Level3 responded to me that they had an issue last night .... but they simply did nothing ... for at least 10 hours they did nothing to fix the issue:
Wow .... Level3 responded to me that they had an issue last night .... but they simply did nothing ... for at least 10 hours they >did nothing to fix the issue:
Any SLA broken? Probably not, that would be a reason to move.
Wow .... Level3 responded to me that they had an issue last night .... but they simply did nothing ... for at least 10 hours they did nothing to fix the issue:
It's more likely that there's a certain amount of nonsense and a lot of
loose ends in the ticketing system; than that the issue resolved itself
without intervention.
You might reasonably conclude that the corrective action and the ticket
are unrelated at least as far as the noc is concerned.
While I can¹t say with any degree of certainty it's related, it¹s somewhat
coincidental that one of one of their west coast customers (Daybreak Games
/ SOE) has been under a fairly hefty DDoS since mid-week. From what I
recall see Daybreak/SOE only uses Level3. (Lots to talk about in that
case.. They¹ve invaded his life.. Not sure I¹d react much better, albeit
privately..)
Can it be somehow related to the DDoS on Telegram (AS62041, AS59930)?
200Gbps SYN flood was what they said on twitter. I don't see 3491 as
an upstream for either ASN any more.
On a side note 3356 became upstream for 62041 about a week ago
I heard so much wrong information in the past 3 days ... Level3 didn't investigate in my packet loss report because there was another incident ongoing and so they thought my report was related to this issue. Even when I updated them AFTER they reported "solved" for the first issue they did nothing ...
Other involved companies did nothing because of 100% incompetence ...