The Pug Commander, on 10 June 2017 - 10:52 AM, said:
With that being said i don't think its PGIs servers
Do you know how BGP peering works? If not then you'll not be able to understand why people with different "ISPs" can all experience the same issues simultaneously. Thats not a knock on you, its network engineering I don't expect you to understand.
While I'm not saying PGI's servers aren't falling over, an explicit statement stating that it the servers are fine, is a strong statement. They have given you one side of the equation, if its not servers side, you must look up stream of the servers.
Its more likely that a large transit provider, both global and/or local has experienced an issue. Major incidents such as those found with Zayo or L3, can disrupt connectivity across the entire northern portion united states(and much more, that is just a scoping example). An instance of such disruptions can occur when route tables are adapting to an AS dropping its BGP sessions with its peer(s). This will result in a update of the route tables and traffic will be shifted/routed/moved elsewhere. If enough traffic suddenly shifts to another AS, you may saturate that peers network(too small of pipeline), overload their cores cpu configuration(unlikely but possible), or several peers ect ect ect.
Anyway...this is wayyyy too technical for a standard end user.
I'll agree with what some people have said however, I'm not so sure it was a good idea to say, "hey, its on your end, figure it out". Typically as a online service provider(software side), you'll want to determine where in the stack the issue is, despite not being an issue with your own servers, your customers are being impacted, so a proper inspection and incident release should be completed...otherwise this happens...witch hunt.
People need something/someone to blame(to make them feel better). Not providing a scapegoat results in mindless conjecture and the blame game.
Edited by Humpday, 10 June 2017 - 09:37 PM.