1
Vraag
2
Reacties
MilenLG

Level 2
  • 8Posts
  • 0Oplossingen
  • 1Likes

I don't have an access to particular servers with internet from Ziggo

Hello, 

 

Since yesterday I don't have an access to my mail server and my website, when I am connected to Ziggo network at home. Same happens with other websites, which are hosted on the same hosting provider's servers. If I use my phone as a hot spot and I use my mobile data (Vodafone), then everything works normal. Any suggestions what might be the issue? 

I tried to reset the modem, nothing changed. The hosting provider is not blacklisted. 

 

Thanks in advance for your help!

 

Cheers, 

Milen

Uitgelicht
MilenLG
topicstarter
Level 2
  • 8Reacties
  • 0Oplossingen
  • 1Likes

Good morning everyone!

In the morning it wasn't working, but now I asked my daughter to check (I am at the office) - it works again.

Thank you all for your efforts to solve this!

Cheers, 

Milen

33 Reacties 33
MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

robinjoo19_0-1651089472122.png

 

AoxoMoxoA

Level 17
T.E.A.M.
  • 3836Posts
  • 80Oplossingen
  • 2888Likes

As @MR_CHIP traced. Almost same results here from tracert in Windows. Network is Ziggo, but other area, then where TS resides in.

 

 

tracing route to server26.superhosting.bg [193.107.36.34]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.<xxx>
  2    17 ms     8 ms    11 ms  dhcp-<xx>.chello.nl [<xxx>]
  3    13 ms    13 ms    11 ms  212.142.53.193
  4    17 ms    14 ms    14 ms  asd-tr0021-cr101-be114-2.core.as33915.net [213.51.7.100]
  5    16 ms    17 ms    14 ms  nl-ams09c-ri1-ae51-0.core.as9143.net [213.51.64.190]
  6    15 ms    16 ms    12 ms  213-46-183-246.aorta.net [213.46.183.246]
  7    22 ms    22 ms    20 ms  fra-eq5-02gw.voxility.net [5.254.73.90]
  8    22 ms    30 ms    19 ms  fra-eq5-01c.voxility.net [109.163.237.18]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    49 ms    46 ms    45 ms  host-185-45-64-218.superhosting.bg [185.45.64.218]
 12    45 ms    44 ms    44 ms  server26.superhosting.bg [193.107.36.34]

 

 

 

Bert

Level 21
T.E.A.M.
  • 75177Posts
  • 5146Oplossingen
  • 21925Likes
  1     1 ms     2 ms     2 ms  192.168.178.1
  2     *        *        *     Request timed out.
  3    12 ms    12 ms    15 ms  tb-rc0001-cr101-et114-201.core.as33915.net [213.51.194.169]
  4    15 ms    15 ms    13 ms  asd-rc0001-cr101-be152-10.core.as9143.net [213.51.158.10]
  5    14 ms    15 ms    13 ms  nl-ams09c-ri1-ae50-0.core.as9143.net [213.51.64.62]
  6    15 ms    14 ms    13 ms  213-46-183-246.aorta.net [213.46.183.246]
  7    20 ms    20 ms    18 ms  fra-eq5-02gw.voxility.net [5.254.73.90]
  8    23 ms    21 ms    20 ms  fra-eq5-01c.voxility.net [109.163.237.18]
  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.
MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

er lijkt echt ergens wat mis te gaan in het netwerk/routering

 

MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

could it be the difference between former ziggo and former upc area that there is a difference in routing somewhere in the network

Bert

Level 21
T.E.A.M.
  • 75177Posts
  • 5146Oplossingen
  • 21925Likes

@MR_CHIP  schreef:

could it be the difference between former ziggo and former upc area that there is a difference in routing somewhere in the network


@MR_CHIP That difference is becoming smaller and smaller, entire parts of the former UPC have already been equated with the former Ziggo area.

MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

then i am out for idea's 

maybe an ziggo moderator can shed some light on the why in this case

looking forward to their response

Bert

Level 21
T.E.A.M.
  • 75177Posts
  • 5146Oplossingen
  • 21925Likes

@MR_CHIP  schreef:

could it be the difference between former ziggo and former upc area that there is a difference in routing somewhere in the network


You are probably right.

There is a difference:

inetnum: 31.151.0.0 - 31.151.255.255
netname: NL-CHELLO-20110217

 

inetnum:        84.26.128.0 - 84.26.191.255
netname:        ZIGGO-CM

MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

i still suspect a entire RIPE/ASN blockade is in place at the hosters end

maybe a ziggo moderator can give an explanation or maybe log/forward the ticket to some network engineers at the NOC 

 

Mark
Oud Community Moderator
Oud Community Moderator
  • 5774Posts
  • 655Oplossingen
  • 1963Likes

Hi all, it seems like all of you who are in the former UPC area can't reach the host, while all of you in the former Ziggo area can reach the host.

 

I've just tested it from the office (in the former UPC area) and indeed, the traceroute ends on the 1st voxility hop, same as in your traceroutes.

Tracing route to milengalabov.com [193.107.36.33]
over a maximum of 30 hops:

  1     4 ms     4 ms     3 ms  192.168.0.1
  2    13 ms    14 ms    13 ms  92-108-249-1.cable.dynamic.v4.ziggo.nl [92.108.249.1]
  3    19 ms    15 ms    17 ms  212.142.4.85
  4    20 ms    18 ms    16 ms  asd-rc0001-cr101-be107-2.core.as33915.net [213.51.7.70]
  5    24 ms    36 ms    25 ms  nl-ams09c-ri1-ae50-0.core.as9143.net [213.51.64.62]
  6    17 ms    22 ms    27 ms  213-46-183-246.aorta.net [213.46.183.246]
  7    23 ms    26 ms    25 ms  fra-eq5-02gw.voxility.net [5.254.73.90]
  8    36 ms    25 ms    24 ms  fra-eq5-01c.voxility.net [109.163.237.18]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

 

After some data gathering I tried again, and to my surprise it works now!

Tracing route to milengalabov.com [193.107.36.33]
over a maximum of 30 hops:

  1     3 ms     4 ms     2 ms  192.168.0.1
  2    16 ms    14 ms    17 ms  92-108-249-1.cable.dynamic.v4.ziggo.nl [92.108.249.1]
  3    11 ms    13 ms    12 ms  212.142.4.85
  4    23 ms    21 ms    22 ms  asd-rc0001-cr101-be107-2.core.as33915.net [213.51.7.70]
  5    18 ms    26 ms    20 ms  nl-ams09c-ri1-ae50-0.core.as9143.net [213.51.64.62]
  6    16 ms    19 ms    18 ms  213-46-183-246.aorta.net [213.46.183.246]
  7    22 ms    25 ms    25 ms  fra-eq5-02gw.voxility.net [5.254.73.90]
  8    26 ms    25 ms    38 ms  fra-eq5-01c.voxility.net [109.163.237.18]
  9    48 ms    52 ms    52 ms  5.254.104.146
 10     *       47 ms    49 ms  40.po1.ar1.sof2.evolink.net [85.14.2.134]
 11    50 ms    51 ms    52 ms  host-185-45-64-218.superhosting.bg [185.45.64.218]
 12    54 ms    47 ms    49 ms  server26.superhosting.bg [193.107.36.33]

 

is the issue fixed for all of you?

MR_CHIP

Level 19
  • 11498Posts
  • 131Oplossingen
  • 3968Likes

@Mark 

im in former upc area and the websites always worked for me

 

robinjoo19_0-1651131524017.png

or is there a difference between some upc area's as well

cause yours says cable.dynamic.v4.ziggo.nl

mine ends with the old name chello.nl

MilenLG
Topicstarter
Level 2
  • 8Posts
  • 0Oplossingen
  • 1Likes

Good morning everyone!

In the morning it wasn't working, but now I asked my daughter to check (I am at the office) - it works again.

Thank you all for your efforts to solve this!

Cheers, 

Milen

Mark
Oud Community Moderator
Oud Community Moderator
  • 5774Posts
  • 655Oplossingen
  • 1963Likes

Hm, so my first conclusion (former-Ziggo vs -UPC) was incorrect... I only checked 2 examples and then found out it started working here. The second conclusion remains, it didn't work at first and now it does!

 

Glad to hear it's been fixed @MilenLG!

AoxoMoxoA

Level 17
T.E.A.M.
  • 3836Posts
  • 80Oplossingen
  • 2888Likes

Just some info from the newspapers, which is probably related to what we have  experienced here.

 

Around the same time various parts of the fibreglass network in France has been sabotaged.

edit:

The ip-adress of Voxility seems to be located in Germany. In a successfull trace the next hop seems also to be located in Germany. So it is hard (for me) to jump into solid conclusions.

 

AoxoMoxoA_0-1651137959302.png

 

 

Link to article in Dutch

E-mail notificaties
Aan Uit

Ontvang een update bij nieuwe reacties in dit topic.

Uitgelicht topic