- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
T-Mobile explains why its network went down, hard, on Monday
Posted on 6/17/20 at 4:08 pm
Posted on 6/17/20 at 4:08 pm
The Verge
quote:
If you’ve been wondering what could knock out one of the United States’ three big cellular carriers’ ability to deliver calls and text messages — and keep it that way for most of an entire day — T-Mobile now has a partial answer that pertains to its extensive nationwide outage Monday.
quote:
The short version, if we’re reading this correctly: a fiber-optic circuit failed, and its backup circuit also failed, which caused a chain reaction that strained the network to the point that many calls and texts couldn’t make it through.
quote:
The longer version:
quote:
Many of our customers experienced a voice and text issue yesterday, specifically with VoLTE (Voice over LTE) calling. My team took immediate action — hundreds of our engineers worked tirelessly alongside vendors and partners throughout the day to resolve the issue starting the minute we were aware of it.
quote:
Our engineers worked through the night to understand the root cause of yesterday’s issues, address it and prevent it from happening again. The trigger event is known to be a leased fiber circuit failure from a third party provider in the Southeast. This is something that happens on every mobile network, so we’ve worked with our vendors to build redundancy and resiliency to make sure that these types of circuit failures don’t affect customers. This redundancy failed us and resulted in an overload situation that was then compounded by other factors. This overload resulted in an IP traffic storm that spread from the Southeast to create significant capacity issues across the IMS (IP multimedia Subsystem) core network that supports VoLTE calls.
We have worked with our IMS (IP Multimedia Subsystem) and IP vendors to add permanent additional safeguards to prevent this from happening again and we’re continuing to work on determining the cause of the initial overload failure.
quote:
It’s not clear which third-party provider’s fiber circuit failed. There was a report on Monday that Level 3, one of the world’s major internet backbone providers, was experiencing an outage, but a spokesperson told TechCrunch differently.
Posted on 6/17/20 at 6:09 pm to AUFan2015
Someone probably rolled out a bad firmware update or something stupid like that.
Posted on 6/17/20 at 6:18 pm to AUFan2015
So A fiber circuit failed and it's backup failed and those individual circuits caused a cascade to bring down it's entire network?
Seems legit
Seems legit
Posted on 6/17/20 at 8:08 pm to Helo
I don't know enough about cell service provider networks to understand how you could have some kinda "ip storm". I know they use a lot of multicast so I kind of wonder if the link failures caused a bug to surface that caused multicast duplication or flooding. That's about all I can think of at that scale.
I've seen a 7609 line card bug out and spew garbage into a layer 2 backbone before, which crippled several core networks within a small isp, but I sincerely doubt T-Mobiles network relies heavily upon layer 2.
I've seen a 7609 line card bug out and spew garbage into a layer 2 backbone before, which crippled several core networks within a small isp, but I sincerely doubt T-Mobiles network relies heavily upon layer 2.
This post was edited on 6/17/20 at 8:12 pm
Posted on 6/18/20 at 7:08 am to AUFan2015
A lot of T-Mobile's network is using voice over IP technology instead of a traditional phone circuit system. The fiber system failed, and the backup system should have routed traffic to prevent the overload but it either failed too or wasn't properly configured. After that all hell broke loose. That's why it was mostly major cities that had the issue. Some of the areas on older tech didn't have the problem.
Posted on 6/18/20 at 3:08 pm to AUFan2015
quote:that's a non-answer. something failed. we already knew that. what about it failed?
a fiber-optic circuit failed, and its backup circuit also failed,
Posted on 6/18/20 at 5:00 pm to arcalades
They were supposed to migrate over a million Sprint users over to the T-Mobile network that day. My guess is that process broke something in regards to routing.
Posted on 6/19/20 at 3:32 pm to AUFan2015
Again it was Cisco.
TMO just fell on the sword for freebies.
TMO just fell on the sword for freebies.
Popular
Back to top
Follow TigerDroppings for LSU Football News