Beantwoord

Poste.it

  • 3 September 2021
  • 7 reacties
  • 148 Bekeken

Hello,

sorry for writing in english but https://poste.it is timing out from my home network .

 

tcptraceroute  poste.it 443
Running:
        traceroute -T -O info -p 443 poste.it
traceroute to poste.it (62.241.12.25), 30 hops max, 60 byte packets
 1  home (192.168.2.254)  0.743 ms  0.665 ms  0.685 ms
 2  1-64-178-143.ftth.glasoperator.nl (143.178.64.1)  3.330 ms  3.709 ms  3.688 ms
 3  10.10.80.102 (10.10.80.102)  6.712 ms  6.630 ms  6.597 ms
 4  10.10.80.149 (10.10.80.149)  6.640 ms  6.237 ms  6.546 ms
 5  217.161.69.141 (217.161.69.141)  7.080 ms  7.129 ms  6.603 ms
 6  ae-10.edge7.Amsterdam1.Level3.net (4.68.70.97)  10.065 ms  8.615 ms  9.264 ms
 7  * * *
 8  213.249.124.222 (213.249.124.222)  28.486 ms  28.269 ms  28.169 ms
 9  93-63-100-10.ip27.fastwebnet.it (93.63.100.10)  26.824 ms  26.971 ms 93-63-100-2.ip27.fastwebnet.it (93.63.100.2)  27.616 ms
10  81-208-11-162.ip.fastwebnet.it (81.208.11.162)  38.053 ms  38.037 ms  37.991 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
 

anything i could check ?

icon

Beste antwoord door Anonymous 3 September 2021, 19:31

Bekijk origineel

7 reacties

Reputatie 7
Badge +15

Hello @samux9292 

I can acces the website via KPN thuis and T-Mobile 4G.

Maybe try changing the DNS servers. Which modem do you have?

https://community.t-mobile.nl/vast-internet-492/wijzigen-t-mobile-thuis-dns-306314

Try 8.8.8.8/8.8.4.4 (Google) for example.

 Hello,

sorry for writing in english but https://poste.it is timing out from my home network .

 

tcptraceroute  poste.it 443
Running:
        traceroute -T -O info -p 443 poste.it
traceroute to poste.it (62.241.12.25), 30 hops max, 60 byte packets
 1  home (192.168.2.254)  0.743 ms  0.665 ms  0.685 ms
 2  1-64-178-143.ftth.glasoperator.nl (143.178.64.1)  3.330 ms  3.709 ms  3.688 ms
 3  10.10.80.102 (10.10.80.102)  6.712 ms  6.630 ms  6.597 ms
 4  10.10.80.149 (10.10.80.149)  6.640 ms  6.237 ms  6.546 ms
 5  217.161.69.141 (217.161.69.141)  7.080 ms  7.129 ms  6.603 ms
 6  ae-10.edge7.Amsterdam1.Level3.net (4.68.70.97)  10.065 ms  8.615 ms  9.264 ms
 7  * * *
 8  213.249.124.222 (213.249.124.222)  28.486 ms  28.269 ms  28.169 ms
 9  93-63-100-10.ip27.fastwebnet.it (93.63.100.10)  26.824 ms  26.971 ms 93-63-100-2.ip27.fastwebnet.it (93.63.100.2)  27.616 ms
10  81-208-11-162.ip.fastwebnet.it (81.208.11.162)  38.053 ms  38.037 ms  37.991 ms
11  * * *
30  * * *
 

anything i could check ?

 

I also did a traceroute and came up with these details;

HOST:                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS???    192.168.1.1      0.0%     1    0.3   0.3   0.3   0.3   0.0
  2. AS50266  143.178.32.1     0.0%     1    2.7   2.7   2.7   2.7   0.0
  3. AS???    10.10.80.106     0.0%     1    3.3   3.3   3.3   3.3   0.0
  4. AS???    10.10.80.145     0.0%     1    3.0   3.0   3.0   3.0   0.0
  5. AS1273   195.89.101.53    0.0%     1    4.9   4.9   4.9   4.9   0.0
  6. AS1299   62.115.154.136   0.0%     1   11.0  11.0  11.0  11.0   0.0
  7. AS1299   62.115.136.194   0.0%     1   34.6  34.6  34.6  34.6   0.0
  8. AS1299   62.115.134.97    0.0%     1   33.7  33.7  33.7  33.7   0.0
  9. AS1299   62.115.115.175   0.0%     1   24.1  24.1  24.1  24.1   0.0
 10. AS1299   62.115.140.253   0.0%     1   33.9  33.9  33.9  33.9   0.0
 11. AS1299   62.115.183.203   0.0%     1   34.9  34.9  34.9  34.9   0.0
 12. AS12874  93.63.100.10     0.0%     1   41.9  41.9  41.9  41.9   0.0
 13. AS12874  81.208.11.162    0.0%     1   52.5  52.5  52.5  52.5   0.0
 14. AS???    ???             100.0     1    0.0   0.0   0.0   0.0   0.0
 15. AS???    62.241.0.209     0.0%     1   63.0  63.0  63.0  63.0   0.0
 16. AS???    ???             100.0     1    0.0   0.0   0.0   0.0   0.0
 17. AS15720  62.241.12.25     0.0%     1   62.8  62.8  62.8  62.8   0.0
 

 

The problem should be resolved and was caused by the routing at fastwebnet. Just compare your and my traceroute. Yours shows the traceroute stopped at 81.208.11.162 where my traceroute continues towards it's final destination.

 

Hello @samux9292 

I can acces the website via KPN thuis and T-Mobile 4G.

Maybe try changing the DNS servers. Which modem do you have?

https://community.t-mobile.nl/vast-internet-492/wijzigen-t-mobile-thuis-dns-306314

Try 8.8.8.8/8.8.4.4 (Google) for example.

It's not caused by DNS issues as the traceroute of @samux9292 shows the domain is resolved to 62.241.12.25, so the DNS server he uses works like a charm.

hello,

8 month later i actually tried again but i have the same issue.

tcptraceroute  poste.it
Selected device br0, address 192.168.2.99, port 45501 for outgoing packets
Tracing the path to poste.it (62.241.12.27) on TCP port 80 (http), 30 hops max
 1  192.168.2.254  0.675 ms  0.541 ms  0.444 ms
 2  1-64-178-143.ftth.glasoperator.nl (143.178.64.1)  3.125 ms  3.188 ms  2.844 ms
 3  10.10.80.102  5.972 ms  6.233 ms  5.994 ms
 4  10.226.4.50  6.055 ms  6.065 ms  6.519 ms
 5  10.10.80.149  5.675 ms  5.627 ms  5.668 ms
 6  217.161.69.141  6.644 ms  6.385 ms  6.218 ms
 7  ae-10.edge7.Amsterdam1.Level3.net (4.68.70.97)  9.459 ms  9.340 ms  14.612 ms
 8  ae2.11.edge1.Milan1.level3.net (4.69.162.225)  24.398 ms  24.362 ms  26.452 ms
 9  213.249.124.222  23.246 ms  23.659 ms  24.257 ms
10  93-63-100-10.ip27.fastwebnet.it (93.63.100.10)  21.910 ms  21.657 ms  21.713 ms
11  81-208-11-162.ip.fastwebnet.it (81.208.11.162)  23.713 ms  23.740 ms  23.422 ms
12  62.241.26.2  35.215 ms  35.030 ms  34.929 ms
13  * * *
14  * * *
15  * * *

 

is there a way i can contact someone from t-mobile for this issue ?

Reputatie 6
Badge +3

Hi @samux9292 ,

As pointed out by @Gerrit078 this problem is within the fastwebnet.it. That's where the trace route stops. 

At hop 7 it leaves the T-Mobile network to Level3 (Transit) which delivers it to fastwebnet. This is not something to be solved by T-Mobile but by fastwebnet. 

Last time it also looked to be a problem at their (fastwebnet) end. 

 

 

 7  ae-10.edge7.Amsterdam1.Level3.net (4.68.70.97)  9.459 ms  9.340 ms  14.612 ms
 8  ae2.11.edge1.Milan1.level3.net (4.69.162.225)  24.398 ms  24.362 ms  26.452 ms
 9  213.249.124.222  23.246 ms  23.659 ms  24.257 ms
10  93-63-100-10.ip27.fastwebnet.it (93.63.100.10)  21.910 ms  21.657 ms  21.713 ms
11  81-208-11-162.ip.fastwebnet.it (81.208.11.162)  23.713 ms  23.740 ms  23.422 ms
12  62.241.26.2  35.215 ms  35.030 ms  34.929 ms
13  * * *
14  * * *
15  * * *

 

is there a way i can contact someone from t-mobile for this issue ?

T-Mobile can't help you with this issue as it's outside of their network, in this case you'll have to get in touch with poste.it and let them know AS15720 has a unstable link towards the servers poste.it have. The issue is at AS15720 which is their own network.

T-Mobile can't even get in touch with poste.it for this as they don't have a direct connection, T-Mobile goes via level3 and right after that towards fastwebnet.it. 

@TechRacing93 Old issue;

10 AS12874 81-208-11-162.ip.fastwebnet.it (81.208.11.162)  38.053 ms  38.037 ms  37.991 ms
11 AS15720 * * *

Current issue;

11 AS12874 81-208-11-162.ip.fastwebnet.it (81.208.11.162)  23.713 ms  23.740 ms  23.422 ms
12 AS15720 62.241.26.2 35.215 ms 35.030 ms 34.929 ms
13 AS15720 * * *

Two different AS numbers where;

AS12874 is known as Fastweb Autonomous System

AS15720 is known as Poste Italiane S.p.A.

 

So in a matter of fact in all cases it's poste.it which has issues going on.

Hi @samux9292 ,

As pointed out by @Gerrit078 this problem is within the fastwebnet.it. That's where the trace route stops. 

At hop 7 it leaves the T-Mobile network to Level3 (Transit) which delivers it to fastwebnet. This is not something to be solved by T-Mobile but by fastwebnet. 

Last time it also looked to be a problem at their (fastwebnet) end. 

 

 

First of all thanks @Gerrit078  and @TechRacing93  for taking time investigating this issue.

i will send an email to poste.it and fastwebnet and i will cross fingers.

 

funny enough t-mobile on mobile can reach poste.it without issues but it goes to a totally different route.

 

❯ tcptraceroute poste.it 443


Selected device en0, address 192.168.186.200, port 49551 for outgoing packets
Tracing the path to poste.it (62.241.12.24) on TCP port 443 (https), 30 hops max
 1  192.168.186.169  3.782 ms  2.401 ms  3.559 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  84.241.225.42  49.495 ms  36.601 ms  43.938 ms
 7  80.157.130.241  40.590 ms  26.038 ms  21.058 ms
 8  pd9ef35f6.dip0.t-ipconnect.de (217.239.53.246)  41.306 ms  34.455 ms  42.225 ms
 9  ae25.amster1.ams.seabone.net (195.22.213.33)  37.894 ms  43.177 ms  42.435 ms
10  et2-0-24-1-110.milano50.mil.seabone.net (195.22.213.13)  64.195 ms  60.868 ms  59.370 ms
11  ibs-asr.milano50.mil.seabone.net (195.22.205.117)  60.324 ms  50.860 ms  57.238 ms
12  * * *
13  * * *
14  * * *
15  host-88-38-116-2.business.telecomitalia.it (88.38.116.2)  90.527 ms  156.966 ms  81.826 ms
16  * * *
17  * * *
18  62.241.12.24 [open]  108.742 ms  81.162 ms  88.004 ms

 

 

First of all thanks @Gerrit078  and @TechRacing93  for taking time investigating this issue.

i will send an email to poste.it and fastwebnet and i will cross fingers.

 

funny enough t-mobile on mobile can reach poste.it without issues but it goes to a totally different route.

 

T-Mobile for Home and T-Mobile Mobile both use different infrastructures and routing. T-Mobile mobile uses Deutsche Telekom AG for everything, while T-Mobile for Home has its own routing policy - fortunately because with the home connections no one wants to have it routed through Deutsche Telekom AG.

It's a shame the information is missing between hops 15 and 18, not that it really changes anything, but I suspect it's the same as what's on hop 16 for me. Anyway, eventually it goes towards AS15720 (62.241.12.2x). I think if you test poste.it on your home connection you will see it's working there again as well.

 

Start: 2022-05-04T18:22:57+0200
HOST: tmobilethuis Loss% Snt Last Avg Best Wrst StDev
1. AS??? 192.168.1.1 0.0% 4 0.3 0.3 0.3 0.4 0.0
2. AS50266 1-32-178-143.ftth.glasoperator.nl 0.0% 4 2.6 2.8 2.6 3.0 0.2
3. AS??? 10.10.80.106 0.0% 4 3.5 3.4 3.3 3.5 0.1
4. AS1273 217.161.98.238 0.0% 4 5.1 6.6 5.0 10.1 2.4
5. AS1273 217.161.98.238 0.0% 4 4.8 6.5 4.8 10.7 2.8
6. AS1299 adm-b1-link.ip.twelve99.net 0.0% 4 5.4 5.5 5.4 5.8 0.2
7. AS1299 adm-bb1-link.ip.twelve99.net 0.0% 4 5.7 5.6 5.5 5.7 0.1
8. AS1299 prs-bb1-link.ip.twelve99.net 0.0% 4 15.7 15.8 15.5 16.5 0.5
9. AS1299 mno-b1-link.ip.twelve99.net 0.0% 4 24.0 23.9 23.9 24.0 0.0
10. AS1299 rom-b2-link.ip.twelve99.net 0.0% 4 33.7 33.6 33.5 33.7 0.1
11. AS1299 fastweb-svc077450-ic366820.c.telia.net 0.0% 4 35.2 35.1 35.0 35.3 0.1
12. AS12874 93-63-100-2.ip27.fastwebnet.it 0.0% 4 33.0 33.0 32.9 33.0 0.0
13. AS12874 81-208-11-162.ip.fastwebnet.it 0.0% 4 35.0 37.0 35.0 43.0 4.0
14. AS15720 62.241.0.210 0.0% 4 42.6 42.6 42.5 42.6 0.1
15. AS15720 62.241.0.209 0.0% 4 45.8 45.7 45.6 45.8 0.1
16. AS??? ??? 100.0 4 0.0 0.0 0.0 0.0 0.0
17. AS15720 62.241.12.20 0.0% 4 48.8 48.9 48.8 49.0 0.1

 

Reageer