*READ FIRST* iBurst Network Status & Issues (DNS, Throughput and Latency)

[Stõrmza]

Same here all international sites are not working.

Youtube is but thats a local provider iBurst uses so yea.

 

[Snotface]

Yep, all international is down for me too.

 

[Stõrmza]

Well still no international what are the chances of the being fixed during this time of year ?

 

[Voodoomon]

Its working now.

Thanks to whoever or whatever got it sorted!

 

[Stõrmza]

Same here thanks for working on it!!! Much appreciated!!

 

[DsBalsak]

Seems like its working again

 

[Psychopompous]

Guardian?

Anyone else having issues loading pages at the Guardian? I keep timing out. Pings do too:

Pinging guardian.co.uk [77.91.249.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 77.91.249.30:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracert suggests a block at their end:

Tracing route to guardian.co.uk [77.91.249.30]
over a maximum of 30 hops:

1 44 ms 39 ms 39 ms lac7.jhb.wbs.co.za [41.213.48.1]
2 66 ms 49 ms 53 ms iburst-41-213-1-2.iburst.co.za [41.213.1.2]
3 70 ms 109 ms 95 ms 192.168.0.113
4 60 ms 42 ms 45 ms pgw04-int-ge03.jhb.wbs.co.za [41.213.126.25]
5 387 ms 261 ms 245 ms gi9-1.223.mag01.lon02.atlas.cogentco.com [149.6.186.169]
6 269 ms 259 ms 253 ms te4-7.ccr01.lon02.atlas.cogentco.com [130.117.50.117]
7 268 ms 259 ms 249 ms te0-4-0-2.ccr21.lon01.atlas.cogentco.com [130.117.0.61]
8 288 ms * 303 ms te1-1.mag02.lon01.atlas.cogentco.com [154.54.74.110]
9 273 ms 245 ms 259 ms 149.11.142.74
10 258 ms 265 ms 289 ms 77.91.255.142
11 279 ms 253 ms 245 ms 77.91.255.146
12 285 ms 264 ms 248 ms 77.91.255.202
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Could they be filtering our IPs? That last IP belongs to them.

 

[ginggs]

Anyone else having issues loading pages at the Guardian? I keep timing out.

I am able to load pages from The Guardian on iBurst, although I am in Cape Town.

Pings do too:

They are not responding to pings from iBurst or my work connection

Could they be filtering our IPs? That last IP belongs to them.

The Guardian could just be blocking ICMP altogether.

 

[r00igev@@r]

The Guardian like many websites is dropping ICMPs on their firewall. They also use a cheaper route to the Internet via cogent. Compare this to BBC that goes via telia.

UNIX has a nice traceroute facility called MTR which shows the packet loss between cogent and The Guardian. However, this might also just be too many ICMPs targeting their network.

BTW: The Guardian web page is poorly designed - it is top heavy - again, compare it to the bbc. See this link: http://thenextweb.com/dd/2013/01/13/30-new-inspiring-responsive-design-websites/2/

My traceroute [v0.80]
redbrick (0.0.0.0) Mon Jan 14 08:12:07 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.111.254 0.0% 35 0.3 0.7 0.3 5.6 1.2
2. sirloin-cr1.jhb.wbs.co.za 0.0% 35 2.1 2.9 1.6 7.5 1.5
3. 192.168.0.113 0.0% 34 4.2 6.2 1.7 83.0 15.2
4. pgw04-int-ge03.jhb.wbs.co.za 0.0% 34 1.8 2.2 1.8 7.8 1.0
5. gi9-1.223.mag01.lon02.atlas.coge 0.0% 34 195.1 210.4 195.0 349.0 43.8
6. te4-7.ccr01.lon02.atlas.cogentco 0.0% 34 344.2 209.2 194.9 344.2 38.5
7. te0-4-0-2.ccr21.lon01.atlas.coge 0.0% 34 195.8 196.1 195.6 198.1 0.6
8. te1-1.mag02.lon01.atlas.cogentco 2.9% 34 195.6 210.2 195.4 374.2 46.5
9. 149.11.142.74 0.0% 34 195.7 206.4 195.4 389.1 41.8
10. 77.91.255.137 0.0% 34 196.1 196.6 195.9 201.4 1.0
11. 77.91.255.194 0.0% 34 196.2 197.5 196.2 207.9 2.1
12. ???

BTW: MTR is available for windoze - winmtr http://winmtr.net/ Excellent little tool.

 

[Psychopompous]

It's back to normal for me too now.

 

[ginggs]

It's back to normal for me too now.

Can you ping or traceroute now?

 

[Psychopompous]

Can you ping or traceroute now?

Should have been clearer, of course: pages are no longer timing out, but diagnostics still are, so r00i is evidently right. The block is newish, as I've not seen this in the past, that I recall.

 

[Violater]

Anyone else having problems in the Durban (Hillcrest / Waterfall) area?
I can't seem to access most sites

 

[r00igev@@r]

Anyone else having problems in the Durban (Hillcrest / Waterfall) area?
I can't seem to access most sites

Apologies for the inconvenience. There was a fibre fault in the area during the early hours of the morning.

 

[Stõrmza]

I have never seen so many big red "X" signs on the iburst webpage, it looks like everything is down is this scheduled maintenance?

 

[Madhawk]

Iburst down tonight. Can't download my scheduled links.

Last night was maintenance night, so don't know what the issue is tonight.

Typed with a cell c connection.

 

[Stõrmza]

Iburst down tonight. Can't download my scheduled links.

Last night was maintenance night, so don't know what the issue is tonight.

Typed with a cell c connection.

Local is working on iBurst, so are some internationals (twitter) although there might be some local provider or somethign similar to youtube.

From the looks of things its affecting 3/4 of the iburst network according to the iburst website. Durban and Capetown have every single link listed as down.

Would be nice if there was some form of communication / news on the website concerning this really annoying.

 

[Land Locked]

Sadly i-burst don't communicate with the customers in any satisfactory or informative way.

 

[r00igev@@r]

Apologies for the problem last night. The fibre provider had a dual path failure.

 

[|3ash3r]

Any problems with tower in Brackenhurst?

Getting this result consistently.