Military Appreciation: Exclusive savings for military, veterans, and their families!
Get superfast AT&T Fiber internet
S

New Member

 • 

3 Messages

Sat, May 16, 2020 5:12 PM

Tecnical Issue with AT&T high speed (fiber) Internet connecting to overseas destination

I've a problem that I cannot make understand to the AT&T tech service. I need to connect this website www.clouditalia.it and to one of their services like e.g. voip.eutelia.it.

Since a couple of days it doesn't work anylonger. At first, I expected the problem to be on their server side, but is not.

I aboslutely need to have my home voip system to connect to voip.eutelia.it [83.211.227.21]. After many months, it does not work any longer.

Here below answers to TRACERT command:

C:\WINDOWS\system32> tracert 83.211.227.21

Tracing route to voip.eutelia.it [83.211.227.21]

over a maximum of 30 hops:

1 3 ms 3 ms 3 ms dsldevice.attlocal.net [192.168.1.254]

2 13 ms 7 ms 8 ms 108-221-36-1.lightspeed.brhmal.sbcglobal.net [108.221.36.1]

3 7 ms 6 ms 8 ms 99.173.217.140

4 9 ms 8 ms 8 ms 99.133.13.148

5 9 ms 10 ms 9 ms 12.83.101.149

6 31 ms 30 ms 29 ms dlstx401igs.ip.att.net [12.123.16.77]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

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.

What above works fine on my cell phone (T Mob ile) and from my neighbours home (W OW provider)

How can I solve the issue?

can the tech reps take care of that ?

Regards,

S

tonydi

ACE - Guru

 • 

4.1K Messages

2年前

It works fine here in CA so there must be some sort of routing issue in the Alabama region. It might be on AT&T's side or some router outside of their network. There's not really anything you can do about it because you'll never get this sort of info up to the NOC engineers by going through any front line support avenue. All you can do is wait it out and hope someone notices the issue and addresses it.

1 <1 ms <1 ms <1 ms 192.168.1.1​

2 1 ms 2 ms 7 ms xxxxxxxxxx.lightspeed.sntcca.sbcglobal.net [xxx.xxx.xxx.xxx]

3 146 ms 99 ms 96 ms 71.148.149.68

4 8 ms 6 ms 6 ms cr2.sffca.ip.att.net [12.123.15.190]​

5 5 ms 3 ms 3 ms 12.122.114.5​

6 3 ms 3 ms 4 ms xe4-2-0.paloalto2.pao.seabone.net [195.22.206.136]​

7 164 ms 164 ms 164 ms et2-1-0.roma52.rom.seabone.net [213.144.177.184]​

8 169 ms 169 ms 169 ms clouditalia.roma52.rom.seabone.net [89.221.32.107]​

9 171 ms 171 ms 172 ms ip-1-72.sn-212-90.clouditalia.com [212.90.1.72]​

10 171 ms 171 ms 171 ms voip.eutelia.it [83.211.227.21]​

New Member

 • 

3 Messages

super thanks for your quick and useful replay!!!

I’d tried to have the customer support rep to understand that.

After 2 hours on the phone... You can guess if I succeed.

Will wait longer.

Thank you again

tonydi

ACE - Guru

 • 

4.1K Messages

Wow, 2 hours of your life that you'll never get back, for nothing. But that's usually how it is with tech support unless your problem is super simple. They're just not trained to deal with anything but simple issues.

Your only hope is that this problem is bigger than just affecting a handful of people and will appear on someone's radar who has the capability to look into it.

Good luck, be safe.

Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

New Member

 • 

5 Messages

I'm also having the same issue with the same exact server, although I'm trying to connect to a different destination (telegram). It's been going on for 2 days now and while it briefly worked last night, it's broken again this morning.

The route always goes through dlstx401igs.ip.att.net [12.123.16.77]
and gets seemingly dropped immediately after.

tracert from last night (working):

Tracing route to telegram.org [149.154.167.99]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 1 ms <1 ms <1 ms [lightspeed.austtx.sbcglobal.net]

3 * * * Request timed out.

4 15 ms 14 ms 15 ms 12.123.240.166

5 7 ms 11 ms 11 ms dlstx401igs.ip.att.net [12.123.16.77]

6 8 ms 7 ms 7 ms 192.205.36.42

7 149 ms 149 ms 149 ms et3-1-2.amster1.ams.seabone.net [195.22.209.211]

8 * * * Request timed out.

tracert from just now (broken):

Tracing route to telegram.org [149.154.167.99]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 6 ms <1 ms <1 ms [lightspeed.austtx.sbcglobal.net]

3 * * * Request timed out.

4 11 ms 15 ms 7 ms 12.123.240.166

5 10 ms 13 ms 9 ms dlstx401igs.ip.att.net [12.123.16.77]

6 * * * Request timed out.

(edited)

tonydi

ACE - Guru

 • 

4.1K Messages

Use an online traceroute tool. You'll find that 149.154.167.99 is down for everyone. Clearly not an AT&T issue.

Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

New Member

 • 

5 Messages

I can access it from my 4G LTE on my phone, it's not down for everyone. DNS is resolving the same IP. I've tried multiple DNS servers and asked friends to check theirs, we all get the same IP for telegram.org -> 149.154.167.99.

What if that traceroute tool you tried is using AT&T on the backend? :)

https://traceroute-online.com/ showed a successful route.

(edited)

New Member

 • 

3 Messages

2年前

Have you been able to solve the issue?

 

The telegram has been barely working for me for the last week and the connection is completely lost today.

 

The support team said it's not their problem since I'm able to visit the "internet".

 

That is my traceroute:

 

tracert telegram.org

 

Tracing route to telegram.org [149.154.167.99]

over a maximum of 30 hops:

 

  1     2 ms     3 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]

  2     3 ms     2 ms     2 ms  107-198-124-1.lightspeed.hstntx.sbcglobal.net [1

07.198.124.1]

  3     *        *        *     Request timed out.

  4    14 ms    15 ms    14 ms  12.122.147.202

  5    24 ms    14 ms    13 ms  12.122.2.197

  6     9 ms    10 ms     9 ms  gar25.dlstx.ip.att.net [12.122.85.233]

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

New Member

 • 

3 Messages

2年前

Same here.

Same big router is not working properly...

 

 

 

Tracing route to telegram.org [149.154.167.99]

over a maximum of 30 hops:

 

  1     3 ms     3 ms     2 ms  192.168.1.254

  2    10 ms     8 ms    11 ms  108-221-36-1.lightspeed.brhmal.sbcglobal.net [108.221.36.1]

  3     *        *        *     Request timed out.

  4    30 ms    30 ms    30 ms  12.240.218.198

  5    32 ms    38 ms    30 ms  attga21crs.ip.att.net [12.122.2.133]

  6    28 ms    30 ms    30 ms  dlstx22crs.ip.att.net [12.122.2.110]

  7    34 ms    34 ms    34 ms  dlstx401igs.ip.att.net [12.123.16.77]

  8    28 ms    28 ms    28 ms  192.205.36.42

  9   149 ms   148 ms   149 ms  et4-0-2.amster1.ams.seabone.net [195.22.209.209]

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

...

 30     *        *        *     Request timed out.

New Member

 • 

8 Messages

1年前

similar problem still exist:

  1     4 ms     3 ms     7 ms  192.168.86.1
  2     5 ms     4 ms     5 ms  192.168.0.1
  3    10 ms     4 ms     4 ms  192.168.1.254
  4     9 ms     5 ms     8 ms  76-244-36-1.lightspeed.sntcca.sbcglobal.net [76.244.36.1]
  5     7 ms     8 ms    14 ms  71.148.135.240
  6    13 ms    12 ms    14 ms  cr2.sffca.ip.att.net [12.123.15.186]
  7    11 ms     8 ms     9 ms  12.122.114.5
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.

ATTHelp

Community Support

 • 

189.1K Messages

1年前

Let's figure out what's going on, @jalen!

 

Do you currently have IPv6 enabled?

 

Let us know so we can assist further!

 

CalebP, AT&T Community Specialist 

New Member

 • 

8 Messages

1年前

Hi, thanks for getting back to me quickly. I am not using IPv6, and IPV6 function has been disabled in the ATT router.

New Member

 • 

8 Messages

1年前

It looks like almost OK now, 12.122.114.5 is back to normal. 

Thanks for your help!

Tracing route to 183.60.124.4 over a maximum of 30 hops

  1     3 ms     6 ms     3 ms  192.168.86.1
  2     6 ms     3 ms     5 ms  192.168.0.1
  3     4 ms     4 ms     4 ms  192.168.1.254
  4     8 ms     8 ms     6 ms  76-244-36-1.lightspeed.sntcca.sbcglobal.net [76.244.36.1]
  5     7 ms     8 ms     6 ms  71.148.135.240
  6    16 ms    13 ms    12 ms  cr2.sffca.ip.att.net [12.123.15.186]
  7    11 ms     8 ms    11 ms  12.122.114.5
  8    15 ms    12 ms    15 ms  192.205.32.78
  9     9 ms    11 ms    11 ms  202.97.50.53
 10   164 ms   165 ms   163 ms  202.97.27.241
 11     *      166 ms     *     202.97.12.14
 12   172 ms   176 ms   177 ms  202.97.94.145
 13   173 ms   171 ms   171 ms  113.108.208.190
 14   165 ms   166 ms   166 ms  121.14.50.66
 15   166 ms   166 ms   165 ms  113.108.218.250
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   163 ms   165 ms   163 ms  183.60.124.4

Trace complete.

ATTHelp

Community Support

 • 

189.1K Messages

1年前

Hi @jalen, thank you for the update. We are delighted your network seems to be back to normal.

 

If you have any additional concerns, please feel free to reach out to us.

Thank you for contacting us on AT&T Community Forums!

 

Lafayette, AT&T Community Specialist

New Member

 • 

8 Messages

1年前

My problem comes back, please help.

TRACERT 183.60.124.4
Tracing route to 183.60.124.4 [183.60.124.4]
over a maximum of 30 hops:

  1     5 ms    15 ms     7 ms  192.168.86.1
  2     5 ms     5 ms     5 ms  192.168.0.1
  3     6 ms     5 ms     5 ms  192.168.1.254
  4     7 ms     7 ms    10 ms  76-244-36-1.lightspeed.sntcca.sbcglobal.net [76.244.36.1]
  5     7 ms     7 ms     9 ms  71.148.135.240
  6     8 ms    15 ms    13 ms  cr2.sffca.ip.att.net [12.123.15.186]
  7    12 ms    12 ms    13 ms  12.122.114.5
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 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.

ATTHelp

Community Support

 • 

189.1K Messages

1年前

Let's get you connected, @jalen!

 

Have you tried using a VPN to access the site? That can allow the connection to sites.

 

If you have the ability to do so, let us know if that helps!


CalebP, AT&T Community Specialist 

New Member

 • 

8 Messages

1年前

I was trying to connect to a VPN server. 
The problem is rather random.

TRACERT 183.60.124.4

Tracing route to 183.60.124.4 over a maximum of 30 hops

  1     1 ms     1 ms     2 ms  192.168.86.1
  2     3 ms     3 ms     2 ms  192.168.0.1
  3     3 ms     2 ms     3 ms  192.168.1.254
  4     6 ms     4 ms     6 ms  76-244-36-1.lightspeed.sntcca.sbcglobal.net [76.244.36.1]
  5     6 ms     4 ms     6 ms  71.148.135.240
  6     8 ms     7 ms    15 ms  cr2.sffca.ip.att.net [12.123.15.186]
  7     6 ms     7 ms     6 ms  12.122.114.5
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 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.

ATTHelp

Community Support

 • 

189.1K Messages

1年前

We're here to help, @jalen 

Here is some information on High latency and ping which may helpful to you. 

Let us know if you have additional questions. 

Deandra, AT&T Community Specialist

New Member

 • 

8 Messages

1年前

The routing issue still exists:

I am wondering, why 12.122.114.5   is always involved? The network latency is reasonably low.

Tracing route to yiyun.n.shifen.com [220.181.111.91]
over a maximum of 30 hops:

  1     2 ms     2 ms     3 ms  192.168.86.1
  2     3 ms     4 ms     5 ms  192.168.0.1
  3     7 ms     5 ms     4 ms  192.168.1.254
  4     9 ms     6 ms     7 ms  76-244-36-1.lightspeed.sntcca.sbcglobal.net [76.244.36.1]
  5     6 ms     8 ms    11 ms  71.148.135.240
  6    11 ms    15 ms    11 ms  cr2.sffca.ip.att.net [12.123.15.186]
  7    12 ms     9 ms    10 ms  12.122.114.5
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *

tonydi

ACE - Guru

 • 

4.1K Messages

1年前

I can get to that address (looks like we're both in NorCal) but it does have a few servers along the way that are just rejecting the ICMP requests.  That's totally normal.  I can ping the destination IP and it's responds.  Are you saying you can't connect to that server?

12.122.114.5 is one of the last AT&T servers along the way, although 202.97.50.73 shows to be in China but that's impossible give the 6ms time.

Tracing route to 220.181.111.91 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  107-218-152-1.lightspeed.sntcca.sbcglobal.net [107.218.152.1]
  3     2 ms     1 ms     1 ms  71.148.149.68
  4     4 ms     6 ms     6 ms  cr2.sffca.ip.att.net [12.123.15.190]
  5     7 ms     4 ms     6 ms  12.122.114.5
  6     5 ms     6 ms     5 ms  192.205.32.78
  7     9 ms     6 ms     6 ms  202.97.50.73
  8   160 ms   157 ms   158 ms  202.97.59.109
  9   146 ms   146 ms   146 ms  202.97.12.117
 10     *        *      146 ms  202.97.48.221
 11   156 ms   156 ms   156 ms  180.149.128.118
 12   158 ms     *        *     36.110.246.209
 13     *        *        *     Request timed out.
 14   157 ms   158 ms   157 ms  106.38.244.150
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18   156 ms   156 ms   156 ms  220.181.111.91

New Member

 • 

8 Messages

1年前

Thanks for looking into it, tonydi

The problem happens time to time. I was not able to access the destination server last night, but now it is working again. For me, the problem always appears at the hops between 12.122.114.5 and  192.205.32.78

Need help?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.