Home Broadband & Home Phone

[perksie Level 58: Overseer]

O2 have acknowledged a broadband service issue and they're investigating.
http://broadband.o2.co.uk/broadbandstat ... bandStatus
A quick workaround is to switch to Google DNS:
8.8.8.8 and
8.8.4.4.
O2 Email appears to be affected as well.

[buseng12 Level 6: Acolyte]

Can't access o2 email either.
This webpage is not available
Google Chrome could not load the webpage because zarkov.shop.o2.co.uk took too long to respond. The website may be down, or you may be experiencing issues with your Internet connection.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the wrench menu > Options > Under the Hood > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 7 (net::ERR_TIMED_OUT): The operation timed out.

Not using o2 dns but 2 independent ones from dns Benchmark. Webpages seem ok apart from this one, could be a site fault.
http://intheworks.co.uk/forum/index.php ... b98a078c8e

[perksie Level 58: Overseer]

The issues appear to be resolved now.

[buseng12 Level 6: Acolyte]

The issues appear to be resolved now.

Nope, connects now but keeps telling me my username and/or password are incorrect. Tried several times & know they are correct.

[perksie Level 58: Overseer]

Different issue - report it.

[buseng12 Level 6: Acolyte]

Different issue - report it.

It was all ok until today's "issue". The same thing happens with one of my secondary accounts as well.

[perksie Level 58: Overseer]

It's fixed now.

[buseng12 Level 6: Acolyte]

It's fixed now.

Confirmed, working ok now.

[npr Level 27: Desk Jockey]

Unfortunately the underlying problem is still there.
I'm guessing this is nothing to do with today's issue and is just network congestion.

87.194.255.155 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.024 | 0.028 | 0.045 | 0.003 | 91.8 |
- Uncached Name | 0.029 | 0.099 | 0.436 | 0.099 | 100.0 |
- DotCom Lookup | 0.040 | 0.070 | 0.190 | 0.038 | 97.8 |
---<-------->---+-------+-------+-------+-------+-------+
87-194-255-155.bethere.co.uk
Be Un Limited
87.194.255.154 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.024 | 0.033 | 0.123 | 0.017 | 98.0 |
- Uncached Name | 0.029 | 0.096 | 0.313 | 0.085 | 100.0 |
- DotCom Lookup | 0.040 | 0.083 | 0.340 | 0.074 | 95.8 |
---<-------->---+-------+-------+-------+-------+-------+
dhr91o08xrgul.cloudfront.net
Be Un Limited

Note: all resolvers on the DNS Benchmark test showed failed lookup's which makes me think it's caused by congestion.
A couple of hours ago, presumably when the network was less busy, all resolvers were at 100% reliable.

[perksie Level 58: Overseer]

There's a bit more here:
http://beusergroup.co.uk/?id=835
I like the "sexy outage message" on the Be helpline!