Unable to Access the Nexus Three Nights in a Row

[Rabbit1251]

Pitchforks and torches!! We will overrun AT&T and be Masters of the U-verse!!

 

 

Marshall of the U-verse Rabbit

[GameTourist]

I'm also on AT&T and was having problems this weekend. The site is fast now though. I'm hoping things stay good because I have enough reasons to hate Comcrap.

 

 

Pitchforks and torches!! We will overrun AT&T and be Masters of the U-verse!!

you, sir, are quite funny!

[GamerRick]

AT&T U-Verse. Northern California Greater San Fransisco Bay Area. On Firefox. Affected from late afternoon through late evening for the past 3 or 4 days.

 

 

Rabbit

 

This applies to me too. And it is domains that have nexusmods.com in them (the entire nexus site for me).

 

Last two nights from 7 PM PST to 1 AM.

Edited October 12, 2015 by GamerRick

[Sleepytime]

woot, first time in about a week ive been able to connect to you guys at this time of day

 

i am on AT&T, West Coast

[CrimJackal]

Dark0ne thanks for continuing to check into the issue. I got ATT support back online tonight. Maybe something was finally spotted on their end.

 

 

I noticed I get Request timed out on pings to nexusmods.com during the outage and tracert also has request timed out. During the day while working both ping and tracert look good.

 

 

From ATT support: "I see there is an issue with the server. However I will escalate this issue to my internal team. My internal team will work on this issue and get back to you through email once it is fixed."

 

 

No other detail though as to what the "issue with the server" was. If I get any email back from ATT, I will let everyone know.

Edited October 13, 2015 by CrimJackal

[Ign0tus]

Nexus still isn't working properly. I've been having issues for about a week. The only way that I can access the site is to use my phone's hotspot to connect my PC to the Internet. Trying to access Nexus through my Uverse connection is an exercise in futility. I'll just let my wallet do the talking. My AT&T Uverse contract is up at the beginning of December. Yes, it's a contract. AT&T Internet sucks so bad that I guess they have to have you sign a contract in order to keep you. Anyway, I always knew that AT&T Internet sucked, but Comcast got to be so expensive that I had to switch last year. When the contract is up, I'm biting the bullet and paying a bit more and going back to Comcast. Slow Internet is useless if I can't even access the sites that I need to access. Even page loading is slow on Uverse. It's a 12Mbps connection. I figured I would just lay off the Usenet this year and I wouldn't notice it. 12Mbps is plenty fast enough for gaming, surfing, email, and Youtube I told myself. Theoretically this is true. In reality, Uverse is horribly slow. I've had very little downtime, I'll give them that, but I had very little downtime with Comcast too. Just general web surfing takes FOREVER with Uverse. It's so slow compared to Comcast when I had it. I'm going back to a 50-100Mbps cable connection. AT&T can stick this garbage where the sun doesn't shine.

 

EDIT: I posted a thread on the AT&T community. Go light that one up too please if you are having issues. This link may work, or you should be able to search their community for "Nexus Mods" and find the thread. Look for both words "Nexus Mods" or you'll get endless topics about the Nexus phone.

https://forums.att.com/t5/Troubleshoot-Internet-Service/Particular-Website-Has-Been-Unavailable-On-Uverse-For-The-Last/m-p/4326593#M5965

Edited October 13, 2015 by Ign0tus

[gator91]

Timeline for me is 5:30PM PST out . Below I have posted the ping and tracing data not sure it helps but here it is and this data in part of the information I provided to ATT..

 

Pinging nexusmods.com [77.72.3.4] with 32 bytes of data:
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Request timed out.
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42
Reply from 77.72.3.4: bytes=32 time=197ms TTL=42
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 77.72.3.4: bytes=32 time=198ms TTL=42

racing route to nexusmods.com [77.72.3.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 23 ms 23 ms 22 ms 12.83.38.189
5 23 ms 31 ms 24 ms ggr2.la2ca.ip.att.net [12.122.128.97]
6 21 ms 23 ms 24 ms las-bb1-link.telia.net [80.239.193.213]
7 34 ms 34 ms 34 ms sjo-b21-link.telia.net [80.91.247.171]
8 35 ms 33 ms 34 ms las-b3-link.telia.net [62.115.138.95]
9 33 ms 33 ms 34 ms pni-as1299-lax2.staminus.net [69.197.1.76]
10 * * * Request timed out.
11 * * 198 ms . [72.8.146.58]
12 * * * Request timed out.
13 198 ms * 197 ms 77-72-3-4.hosted-at.kloud.co.uk [77.72.3.4]

Trace complete.

Current data 6:24AM

C:\Users\gator>ping www.mexusmods.com -t

Pinging www.mexusmods.com [141.8.224.93] with 32 bytes of data:
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=60ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=58ms TTL=241
Reply from 141.8.224.93: bytes=32 time=58ms TTL=241
Reply from 141.8.224.93: bytes=32 time=58ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=57ms TTL=241
Reply from 141.8.224.93: bytes=32 time=58ms TTL=241
Reply from 141.8.224.93: bytes=32 time=56ms TTL=241

Ping statistics for 141.8.224.93:

​

:\Users\gator>tracert www.nexusmods.com

Tracing route to nexusmods.com [77.72.3.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 23 ms 23 ms 22 ms 12.83.38.189
5 23 ms 31 ms 24 ms ggr2.la2ca.ip.att.net [12.122.128.97]
6 21 ms 23 ms 24 ms las-bb1-link.telia.net [80.239.193.213]
7 34 ms 34 ms 34 ms sjo-b21-link.telia.net [80.91.247.171]
8 35 ms 33 ms 34 ms las-b3-link.telia.net [62.115.138.95]
9 33 ms 33 ms 34 ms pni-as1299-lax2.staminus.net [69.197.1.76]
10 * * * Request timed out.
11 * * 198 ms . [72.8.146.58]
12 * * * Request timed out.
13 198 ms * 197 ms 77-72-3-4.hosted-at.kloud.co.uk [77.72.3.4]

Trace complete.

 

​

Edited October 13, 2015 by gator91

[rjminskyrim2]

Success, mostly?

 

I was able to get to Nexus last night using AT&T in So. California around 7:00 pm PDT. It was slower then normal, but was able to update manager & get 3 mods down loaded. It must be the light at the end of the tunnel.

[HippeusOmega]

Success, mostly?

 

I was able to get to Nexus last night using AT&T in So. California around 7:00 pm PDT. It was slower then normal, but was able to update manager & get 3 mods down loaded. It must be the light at the end of the tunnel.

 

I couldn't access the site again all last night not unless I use my 3G signal on my phone and not my wifi. Literally this is frustating me.

[lorca1]

Ok, in my experience, for three days, I've this clear: connection to Nexus starts at about 4-5am local time and ends about 6-7pm. I'm in Northern California using AT&T. I don't get it. If this is indeed an IPv6 issue, then wouldn't Nexus page be disconnected completely instead of in certain hours? Edited October 14, 2015 by lorca1