Skip navigation

Membes not being able to access board.

Forum NavigationHome > Forum Index > Tread Marks > Membes not being able to access board.
Level 16 Human gamer
Alignment: True neutral
Posted on October 5, 2005 at 8:32 pm

If activity to the forums is lower today this is most likely why. http://ask.slashdot.org/askslashdot/05/10/05/2247207.shtml?tid=95&tid=187&tid=4

I know this is affecting KV.

Level 13 Human gamer
Alignment: Chaotic
Posted on October 6, 2005 at 9:26 pm

well, i'm back. Not sure if level3 and cogent worked out their problems, or if my ISP gained access to another link.

Good timing too, need to make some posts.

... not having access to a large (for me) portion of the internet for two days sucks...

Level 13 Extraplanar Programmer
Alignment: Chaotic good
Location: Toronto
Posted on October 7, 2005 at 1:05 pm

I don't think the issue is resolved yet because we still can't contact Wikipedia from the office.

We've been hurting with no Wikipedia.

Level 13 Human gamer
Alignment: Chaotic
Posted on October 7, 2005 at 3:22 pm

well this is fun. I was unable to access this site, or send jim an email an hour ago, now it's working again.

Level 13 Human Shadow
Alignment: Chaotic good
Location: Earth Orbit, Preparing to Attack
Posted on October 7, 2005 at 6:43 pm

Well, it looks like it's back up:

http://scoreboard.keynote.com/scoreboard/Main.aspx?Login=Y&Username=public&Password=public

Level 13 Human gamer
Alignment: True neutral
Posted on October 8, 2005 at 8:21 am

Yup...yup... :D

http://www.putfile.com/boycott-level3.php

Level 15 Human Jack-of-all-trades
Alignment: Chaotic good
Location: The Void
Posted on October 8, 2005 at 1:38 pm

Yeah, I've been working on moving a bunch of equipment to a new collocation facility and had problems with their redundant feed provisioning; one of the circuits showed a theoretical transfer rate of 813Mbps and the other which ran through Level3 reported a rediculously slower transfer rate which I beat on the colo technicians for.

They spent several hours troubleshooting which diagnosis determined was Level3 setting one of their routers to report as overloaded.