- NZNOG - lists.nznog.org

Re: [nznog] Telstra's Outage
by Simon Allard 20 Dec '06

20 Dec '06

Actually, I think it's the other way around. The reason NZ has 3rd rate broadband, is customers expect the world for free. You can't expect good uptimes and run your business which requires high availability internet on a $39.95 DSL account. I agree with everything Dean said, and I bet I am not the only one. -----Original Message----- From: John @ netTRUST [mailto:john(a)nettrust.net.nz] Sent: Thursday, 21 December 2006 11:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Telstra's Outage > Nothing used to piss me off more than the cable customer who used to > compain (without logging trouble tickets BTW) that thier home business > was losing money because their cable modem was down.... > > You buy a residential service - thats what you get. This type of arrogance from a NOC is why NZ has 3rd rate broadband. ADSL and cable are widely marketed to businesses and indeed business connections usually makes up the lions share of revenuw generated by these services. Let's hopen they keep you, and others with the same opinion, in the back room as far from customers as possible -or- put another way you should be using your l33t skills to substantally improve the reliability rather then having too much time on your hands digging for excuses. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

13 17

Re: [nznog] Telstra's Outage
by jdmwoolley＠ihug.co.nz 20 Dec '06

20 Dec '06

John @ netTRUST wrote: > antedotal evidence Erm, perhaps you meant anecdotal? http://www.m-w.com/dictionary/antedotal http://www.m-w.com/dictionary/anecdotal (sorry, couldn't resist - beer!)

1 0

Telstra's Outage
by David Robinson 20 Dec '06

20 Dec '06

Hi, With Telstra's outage taking out the Northern and Western suburbs of Wellington. For what I gather it was a single truck crash bringing down the overhead wires. A single truck crash is a single point of failure, but I remember this email http://list.waikato.ac.nz/pipermail/nznog/2005-June/010158.html which says: "For a start, it takes more than two fibre cuts in the North Island to disrupt us" And also remember back early in the year when one slip on the Hutt motorway took out all services in Wellington. What is so wrong with Telstra's network that single events can affect so many people, when supposable it takes more than two fibre cuts to disrupt them? David

6 5

Re: [nznog] Telstra's Outage
by jdmwoolley＠ihug.co.nz 20 Dec '06

20 Dec '06

David Robinson wrote: > > "For a start, it takes more than two fibre cuts in the North Island to > disrupt us" > > And also remember back early in the year when one slip on the Hutt > motorway took out all services in Wellington. > > What is so wrong with Telstra's network that single events can affect > so many people, when supposable it takes more than two fibre cuts to > disrupt them? This post you've quoted was related to the core network - i.e. the bits that connect Wellington to Auckland etc. This is a fault in the access network i.e. the bit that connects Mary and Bob (or in this case Kandallah) to the core network. NO operator has full redundancy in the access network for residential services. If you want that, you need to pay through the nose to get a business service, even then most services give you only a single copper pair/fibre/cable to your premises which is still a single point of failure. Jonathan

6 5

Re: [nznog] Telstra's Outage
by Scott Weeks 20 Dec '06

20 Dec '06

--- dave.robinson(a)gmail.com wrote: From: "David Robinson" <dave.robinson(a)gmail.com> With Telstra's outage taking out the Northern and Western suburbs of Wellington. For what I gather it was a single truck crash bringing down the overhead wires. A single truck crash is a single point of failure, but I remember this email http://list.waikato.ac.nz/pipermail/nznog/2005-June/010158.html which says: "For a start, it takes more than two fibre cuts in the North Island to disrupt us" And also remember back early in the year when one slip on the Hutt motorway took out all services in Wellington. What is so wrong with Telstra's network that single events can affect so many people, when supposable it takes more than two fibre cuts to disrupt them? ------------------------------------------------------------------- Both fibers are hanging on the same poles? ;-) scott ps. to be ontopic... beer :) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

NZNOG 2007 conference registrations are now open
by Jonny Martin 19 Dec '06

19 Dec '06

(Apologies for duplicates...) Hi All. The New Zealand Network Operators Group (NZNOG) is holding it's annual conference from January 31st to February 2nd 2007 in Palmerston North, New Zealand. Registrations are now open at http://www.nznog.org/registernow.html We encourage you to register early. NZNOG conferences are always lively, educational, and offer a great chance to network with peers from both within NZ and See you there! Jonny.

3 2

International problems via Global-Gateway
by robbie.gernandt＠apn.co.nz 19 Dec '06

19 Dec '06

Hi there Anyone experiencing problems with International connectivity via Global-Gateway? We can't get to www.google.co.nz and a few other sites at the moment I'm still waiting for a response from Global-gateway... PS! International traffic via TelsraClear is fine regards Robbie ******************************************************************************** NOTICE This email and any attachments are confidential. They may contain privileged information or copyright material. If you are not an intended recipient, you should not read, copy, use or disclose the contents without authorisation and we request you contact us at once by return email. Please then delete the email and any attachments from your system. We do not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company. ********************************************************************************

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 18 Dec '06

18 Dec '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS9733 as-name: NZRR-AS9733 descr: Netspace Services Limited descr: WIX peering at '202.7.0.242' descr: see Citylink RT job #7787 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9733 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: operations(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061219 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9733 descr: Route set advertised to AS9439 by Netspace Services Limited - AS9733 members: 203.118.134.64/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: operations(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061219 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Dec '06

17 Dec '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061010 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061019 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.petrie(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Dec '06

13 Dec '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061018 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia (former BCL) - AS24324 members: 124.157.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.106.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061214 source: NZRR

1 0