sadly I doubt many people here will even understand that reference. Are you going to start arguing about outer space teacups next?. Yeah its SEGA we're talking here, but most of this just sounds like conspiracy bullshit no one can prove one way or the other. Logically, given Japan's size they'd probably want to just go ahead and go to a whitelisting style of security checking. Not to mention various random ISP's are getting through aside from JP ones. And really, I'm very much doubting it given SEGA had to be payed off in a contract to block out SEA to begin with. They really would have no reason not to state it by now if it were the case, unless they're waiting for the update to happen. So basically, the redundant nature of the routing protocol kinda baleeted the PSO2 servers from our route?

until all of the backup routers which might know an alternative route were used up - once it got to the last router, that last router passed it off to the first and all these routers modified their routing tables to reflect that. My wild ass guess is that the DDoS attack took down the route to Sega for so long that my ISP's routers tried to reroute themselves from each other - from that Wikipedia article that was posted it looks like routers are made to try to find alternative routes if a certain route is down, so I'm guessing one router tried to route to Sega, found the route dead, passed it off to another router in the infrastructure, that router found it dead, passed it off to the next, etc. Same 5 routes get repeated over and over again and eventually the tracert just gives up (or it hits whatever the routing protocol's definition of infinity is). What happens after it leaves the backbone here in my state - it looks like it hits some sort of aggregator and then the routers just keep passing around the packet to each other. For Roadrunner, it looks like it's a routing loop/backbone issue:īaleeted the first few hops because INTERNETS.

How to use pingzapper