..although technically it was problem upstream, outside their control.
Yesterday, users were reporting: arctele 198.154.109.229 Yes Yes 5060 OK (61 ms)
callcentric 204.11.192.169 Yes Yes 5080 OK (1843 ms) !!!
callwithus 204.74.220.166 Yes Yes 5060 OK (100 ms)
circlenet 192.155.95.111 Yes Yes 5060 OK (74 ms)
denetron 162.213.0.61 Yes Yes 5060 OK (155 ms)
freelycall 178.162.193.12 Yes Yes 80 OK (165 ms)
ideasip 208.97.25.11 Yes Yes 5060 OK (61 ms)
inum 81.201.82.25 Yes Yes 5060 OK (170 ms)
ipcomms-1 64.154.41.150 Yes Yes 5060 OK (59 ms)
ipcomms-2 64.154.41.158 Yes Yes 5060 OK (73 ms)
localphone 94.75.247.45 Yes Yes 5060 OK (156 ms)
sipbroker 204.11.194.10 Yes Yes 5060 OK (71 ms)
sipsorcery 67.222.131.147 Yes Yes 5060 OK (70 ms)
So what happened?On 12 August 2014, the internet hit an arbitrary limit of more than 512K routes. This 512K route limit is something we have known about for some time.The fix for Cisco devices – and possibly others – is fairly straightforward. Internet service providers and businesses around the world chose not to address this issue in advance, as a result causing major outages around the world. ~ Trevor Pott
Read the rest here. Or here. | 