NTL broadband down today?

electro.ie

Anyone else having problems with NTL broadband, I have the 6meg and am in Dublin 9 and cant access anything. Cant renew the ip (192.168.100.11) and furthermore I've been on hold on the customer support line for more than an hour and a half.

Sad Professor

Mine is fine. In fact I almost never have any problems with NTL broadband, touch wood.

electro.ie

It's well for some.... it wont be long until you do

Sad Professor

electro.ie wrote:

It's well for some.... it wont be long until you do

You maybe right but I've had it for 3 years and had plenty of problems in the beginning so I know well what its like. NTL's customer support is terrible.

JNive

NTL and Chorus have been offline for a bit today, why?

The chorus network appears to be shifted over to the ntlworld.ie ip/routing space as of a few hours ago, or so my traceroutes are telling me.
Traffic appears to be having issues when exiting the aorta.net backbone in amsterdam, france and washington. so id assume there are some BGP updates in progress along with routing reconfigurations.

JNive

Anyways, im able to post by using a proxy server on one of my machines in dallas.

It would appear that the previous ip that was being allocated to me by chorus which was registered as a Chorus IP for HSD Subscribers in Cork, is on AS6830 and is currently announced correctly as such. And therefore being routed to correctly.

However today ive seen that i am now being allocated an IP registered as an NTL Communications ( ntlworld.ie ) Address. This is IP is not on the AS5089 which was used by NTL at INEX, and when doing a BGP trace, is reported as AS0 which throws a not found/error page, leading me to believe that these are new ips being allocated or at least, a new AS Route being created, and is currently not announcing properly yet, and thus inbound traffic understandably has problems trying to figure out how to route to AS0 lol.

UPDATE: checked the ripe database directly, and this IP subnet is indeed registered under AS6830, and is as yet still not listed or announcing at INEX . bummer. However there is still routing anomolies ocurring on exiting/entering the aorta backbones

UPDATE2: Appears as though some inbound routes attempt to come through 213.46.165.10 which is not responding. however 213.46.165.18 routes work ok.

dloob

It's working again in Galway after 5 days down.
The routing has changed it's not going through Amsterdam anymore.

Tracing route to [url]www.boards.ie[/url] [82.195.136.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WRT54GL [192.168.1.1]
  2    36 ms     5 ms     5 ms  10.92.96.1
  3    32 ms    35 ms    13 ms  089-101-162193.ntlworld.ie [89.101.162.193]
  4    11 ms     9 ms    11 ms  dbln-t2core-a-ge-2-1-0-0.aorta.net [213.46.165.5
]
  5    20 ms    19 ms    19 ms  uk-lon01a-rd2-pos-1-2.aorta.net [213.46.160.17]

  6    48 ms    25 ms    30 ms  uk-lon01a-ri2-pos-4-0.aorta.net [213.46.174.142]

  7    40 ms    38 ms    40 ms  ge9-0.mpr2.lhr1.uk.above.net [195.66.226.76]
  8    63 ms    69 ms    74 ms  213.161.92.158
  9    66 ms    49 ms    68 ms  82.195.143.4
 10    54 ms     *       49 ms  boards.ie [82.195.136.250]

Trace complete.

DemonOfTheFall

I'm still routing through amsterdam, 100ms+ pings to boards.

dub45

As a detached observer it would seem logical to notify customers if maintenance was going to be carried out?

JNive

Notify ? lol, not when chorus/UPC are involved lol. cause that requires planning lol.

JNive

just goes to show how bad their routing really is, even though you and I are on the same AS , we take different routes. If there was any sort of coherent or centralised routing policy, we would go through the same route outside the NTL network, but noooooo lol.

Tracing route to boards.ie [82.195.136.250]
over a maximum of 30 hops:

  1     5 ms     7 ms     4 ms  089-101-2320XX.ntlworld.ie [89.101.232.XX]
  2     9 ms    18 ms    13 ms  089-101-232001.ntlworld.ie [89.101.232.1]
  3   151 ms   204 ms    19 ms  089-101-163049.ntlworld.ie [89.101.163.49]
  4   224 ms    24 ms    23 ms  dbln-t2core-b-ge-2-2-0-0.aorta.net [213.46.165.1
7]
  5     *       52 ms    48 ms  nl-ams-rc-01-pos-0-1.chellonetwork.com [213.46.1
60.13]
  6    66 ms   191 ms    48 ms  nl-ams09a-ri1-ge-5-0.aorta.net [213.46.183.81]
  7   154 ms    53 ms    55 ms  GigabitEthernet3-2.core2.ams1.level3.net [195.69
.144.110]
  8   136 ms    49 ms   111 ms  ae-0-54.mp2.Amsterdam1.Level3.net [4.68.120.98]

  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    73 ms    78 ms    82 ms  80.253.124.21
 12   148 ms    77 ms    76 ms  82.195.143.132
 13    75 ms    75 ms   218 ms  boards.ie [82.195.136.250]

Trace complete.

Just to make things clear, im on Chorus in Cork

Current UPC Routing Info can be found at
http://www.ripe.net/fcgi-bin/whois?searchtext=AS6830&form_type=simple


This is a traceroute from my server nyc-2.dsi-gaming.com to my current IP

 1  69.9.176.253 (69.9.176.253)  0.717 ms  0.395 ms  0.375 ms
 2  5.ae0.cr1.lga2.us.voxel.net (69.9.166.97)  0.499 ms  0.320 ms  0.291 ms
 3  820.ae0.cr2.lga1.us.voxel.net (69.9.185.124)  0.615 ms 825.ae0.cr2.lga1.us.voxel.net (69.9.166.50)  0.563 ms 820.ae0.cr2.lga1.us.voxel.net (69.9.185.124)  0.530 ms
 4  US-NY-RI-01.chello.com (198.32.160.48)  5.837 ms  0.545 ms  0.597 ms
 5  us-nyc01b-rd1-pos-1-0.aorta.net (213.46.190.169)  1.298 ms  1.130 ms  1.211 ms
 6  uk-lon01a-rd2-pos-6-0.aorta.net (213.46.160.125)  70.800 ms  70.805 ms  72.789 ms
 7  pl-waw01a-rd1-pos-4-0-0.aorta.net (213.46.160.18)  83.712 ms  83.120 ms  83.023 ms
 8  213.46.165.6.aorta.net (213.46.165.6)  82.997 ms  83.103 ms  82.906 ms
 9  *

This is the same traceroute from me out to it.

Tracing route to nyc-2.dsi-gaming.com [69.9.176.254]
over a maximum of 30 hops:

  1     3 ms     4 ms     3 ms  089-101-2320XX.ntlworld.ie [89.101.232.XX]
  2    14 ms    10 ms    13 ms  089-101-232001.ntlworld.ie [89.101.232.1]
  3    20 ms    23 ms    18 ms  089-101-163049.ntlworld.ie [89.101.163.49]
  4    22 ms    20 ms    22 ms  dbln-t2core-b-ge-2-2-0-0.aorta.net [213.46.165.1
7]
  5    51 ms    51 ms    49 ms  nl-ams-rc-01-pos-0-1.chellonetwork.com [213.46.1
60.13]
  6    98 ms   249 ms    50 ms  nl-ams02a-ra1-ge-4-0-0-0.aorta.net [213.46.183.9
7]
  7     *        *        *     Request timed out.

As i said, thank god for me being able to setup a proxy server on one of the machines that UPC can actually route to, and as such not having half the websites on the net unavailable.

Also, this is a traceroute to dloob above.

traceroute to 89.101.162.193 (89.101.162.193), 30 hops max, 46 byte packets
 1  69.9.176.253 (69.9.176.253)  0.443 ms  0.398 ms  0.398 ms
 2  5.ae0.cr1.lga2.us.voxel.net (69.9.166.97)  0.275 ms  0.313 ms  0.295 ms
 3  820.ae0.cr2.lga1.us.voxel.net (69.9.185.124)  0.598 ms 825.ae0.cr2.lga1.us.voxel.net (69.9.166.50)  30.917 ms 820.ae0.cr2.lga1.us.voxel.net (69.9.185.124)  0.491 ms
 4  US-NY-RI-01.chello.com (198.32.160.48)  0.671 ms  0.922 ms  1.043 ms
 5  us-nyc01b-rd1-pos-1-0.aorta.net (213.46.190.169)  1.346 ms  1.322 ms  1.341 ms
 6  uk-lon01a-rd1-pos-6-0.aorta.net (213.46.160.153)  70.027 ms  68.738 ms  68.889 ms
 7  uk-lon01a-rd2-10ge-7-0.aorta.net (213.46.174.34)  70.692 ms  70.772 ms  70.779 ms
 8  pl-waw01a-rd1-pos-4-0-0.aorta.net (213.46.160.18)  81.153 ms  81.104 ms  81.245 ms
 9  213.46.165.10.aorta.net (213.46.165.10)  81.512 ms * *

seems as though the issue is with the same group of routers, in the 213.46.165.xx range on the inbound routes.

dloob

Hi JNive
This is my trace to your server.
From Dublin to Holland to the UK then off to the US.
I'm on NTL in Galway.

Tracing route to nyc-2.dsi-gaming.com [69.9.176.254]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WRT54GL [192.168.1.1]
  2    15 ms    11 ms    36 ms  10.92.96.1
  3    18 ms    25 ms    38 ms  089-101-162193.ntlworld.ie [89.101.162.193]
  4    10 ms    14 ms    11 ms  dbln-t2core-a-ge-2-1-0-0.aorta.net [213.46.165.5
]
  5    22 ms    21 ms    19 ms  nl-ams-rc-02-pos-2-0.chellonetwork.com [213.46.1
60.17]
  6    30 ms    33 ms    50 ms  uk-lon01a-rd1-10ge-7-0.aorta.net [213.46.174.33]

  7   107 ms    89 ms    98 ms  us-nyc01b-rd1-pos-10-0.aorta.net [213.46.160.154
]
  8    96 ms    99 ms    93 ms  us-nyc02a-ri2-so-2-0-0-0.aorta.net [213.46.190.1
70]
  9   113 ms   135 ms    91 ms  nyiix1.voxel.net [198.32.160.128]
 10    91 ms   124 ms   107 ms  820.ae0.cr1.lga2.us.voxel.net [69.9.185.122]
 11    94 ms   115 ms   100 ms  5.ge0-1.esr1.d1.lga2.us.voxel.net [69.9.166.102]

 12    93 ms   112 ms   107 ms  69.9.176.254

Trace complete.

dub45

What's UPC's reputation like in other countries?

JNive

yup, its looking like a routing issue in amsterdam from the looks of it. some people's traffic goes the right route, others are on the bad route. the fact that yours goes IE>AMS>UK>US whereas mine goes IE>AMS>AMS and stops suggests that my traffic and possibly others is yet to get redirected/corrected around the fault/issue