The New Zealand Network Operators' Group
The New Zealand Network Operators' Group (NZNOG) has no king, president
or formal membership. It consists of the subscribers to this mailing
list. The group is intended to facilitate discussion among operators of
networks in New Zealand on matters relevant to network operators as
described in the list's Acceptable Use Policy. That policy appears later
in this posting.
Conference
Our next conference is to be hosted by FX Networks in Auckland on 28-30
January 2009. Registration is now open. For more information see
http://2009.nznog.org/ .
Other Meetings
See http://thursdaynightcurry.com/ if you live in or near Auckland,
Hamilton or Wellington.
Operators' Contact List
See http://www.nznog.org/?page_id=6 for operational contact details for
most New Zealand ISP's. These are intended for use by other network
operators, not by most customers.
Internet Exchanges
See http://www.nzix.net/ for details of exchanges in operation.
About This Mailing List
This list has around 1000 addresses subscribed. You may only post to the
list from a subscribed address. A number of people subscribe
addresses which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of APN Online, Citylink, and
The University of Waikato. None of these organisations, nor any
administrator, is responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ .
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
--
Donald Neal | "Careful design and strict discipline are
Research Officer | necessary to prevent this sort of mess
WAND | from escaping the development laboratory
The University of Waikato | and infesting the production environment."
| - D. Russell
Anyone know the geographical extent of the outage it all died here in
Katikat at 2208pm no PPP.
Dreadful customer service. No notice and no advice during outage.
Maurice
-----Original Message-----
From: nznog-request(a)list.waikato.ac.nz
[mailto:nznog-request(a)list.waikato.ac.nz]
Sent: Saturday, 29 November 2008 12:00 p.m.
To: nznog(a)list.waikato.ac.nz
Subject: NZNOG Digest, Vol 71, Issue 22
Send NZNOG mailing list submissions to
nznog(a)list.waikato.ac.nz
To subscribe or unsubscribe via the World Wide Web, visit
http://list.waikato.ac.nz/mailman/listinfo/nznog
or, via email, send a message with subject or body 'help' to
nznog-request(a)list.waikato.ac.nz
You can reach the person managing the list at
nznog-owner(a)list.waikato.ac.nz
When replying, please edit your Subject line so it is more specific than
"Re: Contents of NZNOG digest..."
Today's Topics:
1. Xtra are Broked... (Mark Foster)
2. Re: Xtra are Broked... (Bill Walker)
3. Re: Xtra are Broked... (Kyle Carter)
4. Re: Xtra are Broked... (Mark Foster)
5. Re: Xtra are Broked... (Philip Seccombe)
----------------------------------------------------------------------
Message: 1
Date: Fri, 28 Nov 2008 21:53:25 +1300 (NZDT)
From: Mark Foster <blakjak(a)blakjak.net>
Subject: [nznog] Xtra are Broked...
To: NZNOG(a)list.waikato.ac.nz
Message-ID: <Pine.LNX.4.64.0811282152100.2262(a)skyhawk.blakjak.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> www.xtra.co.nz
Server: alien.xtra.co.nz
Address: 202.27.184.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to alien.xtra.co.nz timed-out
At this point in time noone i've spoken with appears to be able to talk DNS
to Xtra, which is having flow on effects as you may imagine (i.e. MX records
aren't being supplied).
A headsup for those who havn't already noticed.
Mark.
------------------------------
Message: 2
Date: Fri, 28 Nov 2008 22:43:17 +1300
From: Bill Walker <Bill.Walker(a)staff.snap.net.nz>
Subject: Re: [nznog] Xtra are Broked...
To: "NZNOG(a)list.waikato.ac.nz" <NZNOG(a)list.waikato.ac.nz>
Message-ID:
<450C73DF8617BA44AA8BE812B3E921AC03F7293CAD(a)TOM.staff.snap.net.nz>
Content-Type: text/plain; charset="us-ascii"
All traffic dropped off at 9pm, DNS disapeared and so did their routes.
We've been trying to get hold of Telecom by phone and email, no luck so far.
Broadband users are still connected, but if they disconnect they can't
reconnect.
Cheers,
Bill
________________________________________
From: Mark Foster [blakjak(a)blakjak.net]
Sent: Friday, 28 November 2008 9:53 p.m.
To: NZNOG(a)list.waikato.ac.nz
Subject: [nznog] Xtra are Broked...
> www.xtra.co.nz
Server: alien.xtra.co.nz
Address: 202.27.184.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to alien.xtra.co.nz timed-out
At this point in time noone i've spoken with appears to be able to talk DNS
to Xtra, which is having flow on effects as you may imagine (i.e. MX records
aren't being supplied).
A headsup for those who havn't already noticed.
Mark.
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.10/1813 - Release Date: 27/11/2008
9:02 a.m.
------------------------------
Message: 3
Date: Sat, 29 Nov 2008 09:42:08 +1300
From: "Kyle Carter" <kyle(a)feet.net.nz>
Subject: Re: [nznog] Xtra are Broked...
To: <NZNOG(a)list.waikato.ac.nz>
Message-ID: <3AB24E0C024548EAA59D8671AA6C5E29(a)Game>
Content-Type: text/plain; charset="us-ascii"
Telecom sure had issues last night
My dsl wouldn't pass any traffic, and then after rebooting the dsl modem I
couldn't get any PPP.
Im back online now (after giving up and going to bed), but couldn't get hold
of anyone on the xtra helpdesk. Trying to contact them resulted in dropped
calls, or beeping (as in no such extension) after being forwarded from the
'some xtra users are having issues surfing websites' message..
Xtras website I couldn't get to from my iphone.. telecoms website was also
down..
The automated message on the phone system said 'no known problems on the
xtra network' however if you chose to talk to a technical support person
you got a message saying there was a fault with surfing and checking email.
No ETA.
If someone from xtra is on the list, how about you put a decent procedure
for changing outage notification messages. And ensuring that your phones
maybe don't rely on the same infastructure?
Just my rant for the week..
Does anyone know what kind of failure was needed for this error? Or was it
just a list of separate systems that all died. (it is the leadup to xmas,
everything starts to break then)
Kyle Carter
-----Original Message-----
From: Bill Walker [mailto:Bill.Walker(a)staff.snap.net.nz]
Sent: Friday, 28 November 2008 10:43 p.m.
To: NZNOG(a)list.waikato.ac.nz
Subject: Re: [nznog] Xtra are Broked...
All traffic dropped off at 9pm, DNS disapeared and so did their routes.
We've been trying to get hold of Telecom by phone and email, no luck so far.
Broadband users are still connected, but if they disconnect they can't
reconnect.
Cheers,
Bill
________________________________________
From: Mark Foster [blakjak(a)blakjak.net]
Sent: Friday, 28 November 2008 9:53 p.m.
To: NZNOG(a)list.waikato.ac.nz
Subject: [nznog] Xtra are Broked...
> www.xtra.co.nz
Server: alien.xtra.co.nz
Address: 202.27.184.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to alien.xtra.co.nz timed-out
At this point in time noone i've spoken with appears to be able to talk DNS
to Xtra, which is having flow on effects as you may imagine (i.e. MX records
aren't being supplied).
A headsup for those who havn't already noticed.
Mark.
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.10/1813 - Release Date: 27/11/2008
9:02 a.m.
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
------------------------------
Message: 4
Date: Sat, 29 Nov 2008 09:48:42 +1300 (NZDT)
From: Mark Foster <blakjak(a)blakjak.net>
Subject: Re: [nznog] Xtra are Broked...
To: Kyle Carter <kyle(a)feet.net.nz>
Cc: NZNOG(a)list.waikato.ac.nz
Message-ID: <Pine.LNX.4.64.0811290944190.9273(a)skyhawk.blakjak.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sat, 29 Nov 2008, Kyle Carter wrote:
> Telecom sure had issues last night
>
> My dsl wouldn't pass any traffic, and then after rebooting the dsl
> modem I couldn't get any PPP.
Classic example of why 'Reboot your Router' is often not the right advice; a
partial breakage (based on reports, DNS failed but access for many customers
kept working) escalates to full breakage when you reboot (failure to
establish PPP links). I've heard reported that people were able to surf
once they set up alternative DNS servers.
> Im back online now (after giving up and going to bed), but couldn't
> get hold of anyone on the xtra helpdesk. Trying to contact them
> resulted in dropped calls, or beeping (as in no such extension) after
> being forwarded from the 'some xtra users are having issues surfing
websites' message..
>
> Xtras website I couldn't get to from my iphone.. telecoms website was
> also down..
This morning I can't get to http://xtra.co.nz/help but (of course)
http://xtra.co.nz redirects to Yahoo just fine.
http://www.telecom.co.nz was down overnight, and now points to a 'scheduled
upgrade' notice.
I can however receive responses to DNS queries to alien.xtra.co.nz this
morning, which is a big plus.
> The automated message on the phone system said 'no known problems on the
> xtra network' however if you chose to talk to a technical support person
> you got a message saying there was a fault with surfing and checking
email.
> No ETA.
Have to concur that automated systems like this need some consistency.
'no known problems' makes a farce of the system, I for one never take
automated messages like that seriously from Telecom anymore.
After over an hour on a hold queue last night, I too gave up and went to
bed.
> If someone from xtra is on the list, how about you put a decent procedure
> for changing outage notification messages. And ensuring that your phones
> maybe don't rely on the same infastructure?
Whilst I agree, I also hear rumours of a power failure at MDR. That'd
break all manner of things, I presume.
Mark.
------------------------------
Message: 5
Date: Sat, 29 Nov 2008 11:54:38 +1300
From: "Philip Seccombe" <philip(a)turnstone.co.nz>
Subject: Re: [nznog] Xtra are Broked...
To: "Mark Foster" <blakjak(a)blakjak.net>, "Kyle Carter"
<kyle(a)feet.net.nz>
Cc: NZNOG(a)list.waikato.ac.nz
Message-ID:
<D775FE22DA44E145A612D100966B6E0A449353(a)server.truetechnologies.local>
Content-Type: text/plain; charset="iso-8859-1"
The Site maintenance message is amusing, 1400pm huh?
"Unfortunately the www.telecom.co.nz website is unavailable right now as we
are upgrading our system between the hours of 08:00 and 14:00pm 29
November."
I'll be sure not to reboot my router, sounds pretty serious
Philip Seccombe
-----Original Message-----
From: Mark Foster [mailto:blakjak(a)blakjak.net]
Sent: Sat 11/29/2008 9:48 AM
To: Kyle Carter
Cc: NZNOG(a)list.waikato.ac.nz
Subject: Re: [nznog] Xtra are Broked...
On Sat, 29 Nov 2008, Kyle Carter wrote:
> Telecom sure had issues last night
>
> My dsl wouldn't pass any traffic, and then after rebooting the dsl modem I
> couldn't get any PPP.
Classic example of why 'Reboot your Router' is often not the right advice;
a partial breakage (based on reports, DNS failed but access for many
customers kept working) escalates to full breakage when you reboot
(failure to establish PPP links). I've heard reported that people were
able to surf once they set up alternative DNS servers.
> Im back online now (after giving up and going to bed), but couldn't get
hold
> of anyone on the xtra helpdesk. Trying to contact them resulted in
dropped
> calls, or beeping (as in no such extension) after being forwarded from
the
> 'some xtra users are having issues surfing websites' message..
>
> Xtras website I couldn't get to from my iphone.. telecoms website was also
> down..
This morning I can't get to http://xtra.co.nz/help but (of course)
http://xtra.co.nz redirects to Yahoo just fine.
http://www.telecom.co.nz was down overnight, and now points to a
'scheduled upgrade' notice.
I can however receive responses to DNS queries to alien.xtra.co.nz this
morning, which is a big plus.
> The automated message on the phone system said 'no known problems on the
> xtra network' however if you chose to talk to a technical support person
> you got a message saying there was a fault with surfing and checking
email.
> No ETA.
Have to concur that automated systems like this need some consistency.
'no known problems' makes a farce of the system, I for one never take
automated messages like that seriously from Telecom anymore.
After over an hour on a hold queue last night, I too gave up and went to
bed.
> If someone from xtra is on the list, how about you put a decent procedure
> for changing outage notification messages. And ensuring that your phones
> maybe don't rely on the same infastructure?
Whilst I agree, I also hear rumours of a power failure at MDR. That'd
break all manner of things, I presume.
Mark.
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
--
This message was scanned by the Turnstone managed spam filter and is
believed to be clean.
> www.xtra.co.nz
Server: alien.xtra.co.nz
Address: 202.27.184.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to alien.xtra.co.nz timed-out
At this point in time noone i've spoken with appears to be able to talk
DNS to Xtra, which is having flow on effects as you may imagine (i.e. MX
records aren't being supplied).
A headsup for those who havn't already noticed.
Mark.
Hi all,
Registration for the NZNOG09 conference is now open. Please do
register early.
http://2009.nznog.org/register
We're being hosted by FX Networks at the Mount Richmond Hotel and
Conference Centre in Mt. Wellington, Auckland from Wednesday 28 to
Friday 30th January.
We haven't had a conference in Auckland for quite some years now, so
this is the perfect opportunity for all those Aucklanders who find it
difficult to travel to get there.
The initial list of talks is online now. The website will be updated
over the coming days and weeks with full details and additional
speakers as they are confirmed.
Speakers for NZNOG09 include James Spenceley (Vocus), Bill Manning
(EP.NET) James Sinclair (PIPE Networks), IANA, Gordon Paynter
(National Library), and many other quality speakers.
Tutorials on offer are the Sysadmin Miniconf, Security, IPv6, and
DNSSEC/DNS operations.
Block accommodation, as in virtually the entire hotel, has been
arranged at $110 per night. This is bookable through the NZNOG09
registration site. Twin rooms are available for those wishing to keep
costs down.
Once again the conference fees have been kept down at just $225 for
the three days. This includes both the vendor/sponsor cocktail
reception on the Wednesday night and conference dinner on the Thursday
night, and lunch and tea breaks on all three days.
In addition to providing a superb backdrop for social functions, the
outdoor pool also provides a perfect medium for the Perry Lorrier
IPoSomething challenge :).
Now is the time to approach your boss and obtain approval to get to
the conference.
Cheers,
Jonny.
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9281:RS-ROUTES:AS9503
descr: advertised to AS9281 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081118
source: NZRR
REPLACED BY:
route-set: AS9281:RS-ROUTES:AS9503
descr: advertised to AS9281 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081127
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS17746
descr: advertised to AS9560 by Orcon Internet Limited - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
156.62.0.0/16^16-29,
202.150.96.0/19^19-29,
203.99.0.0/19^19-29,
203.96.192.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
116.193.144.0/21^21-29,
116.199.208.0/21^21-29,
210.54.56.0/21^21-29,
210.79.48.0/21^21-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.77.0/24^24-29,
202.36.170.0/24^24-29,
202.37.19.0/24^24-29,
202.37.173.0/24^24-29,
202.37.194.0/24^24-29,
202.49.187.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.167.0/24^24-29,
202.50.246.0/24^24-29,
202.174.160.0/24^24-29,
203.86.200.0/24^24-29,
210.54.12.0/24^24-29,
210.55.1.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29,
210.55.180.128/26^26-29,
210.55.193.64/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081016
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17746
descr: advertised to AS9560 by Orcon Internet Limited - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
156.62.0.0/16^16-29,
202.150.96.0/19^19-29,
203.99.0.0/19^19-29,
203.96.192.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
116.193.144.0/21^21-29,
116.199.208.0/21^21-29,
210.54.56.0/21^21-29,
210.79.48.0/21^21-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
120.138.22.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.77.0/24^24-29,
202.36.170.0/24^24-29,
202.37.19.0/24^24-29,
202.37.173.0/24^24-29,
202.37.194.0/24^24-29,
202.49.187.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.167.0/24^24-29,
202.50.246.0/24^24-29,
202.174.160.0/24^24-29,
203.86.200.0/24^24-29,
210.54.12.0/24^24-29,
210.55.1.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29,
210.55.180.128/26^26-29,
210.55.193.64/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081127
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS45279:RS-ROUTES:AS9503
descr: advertised to AS45279 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081118
source: NZRR
REPLACED BY:
route-set: AS45279:RS-ROUTES:AS9503
descr: advertised to AS45279 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081127
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081115
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081127
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081115
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,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.124.106.0/23^23-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081127
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS4770
descr: advertised to AS9560 by ICONZ Ltd - AS4770
members: 210.48.0.0/17^17-29,
210.185.0.0/18^18-29,
210.54.160.0/19^19-29,
114.134.160.0/20^20-29,
202.55.96.0/20^20-29,
202.174.160.0/20^20-29,
210.56.32.0/20^20-29,
114.134.176.0/21^21-29,
120.138.16.0/21^21-29,
202.12.248.0/21^21-29,
202.37.144.0/21^21-29,
202.37.224.0/21^21-29,
202.74.224.0/21^21-29,
202.78.240.0/21^21-29,
202.36.36.0/22^22-29,
202.37.140.0/22^22-29,
202.37.200.0/22^22-29,
202.41.136.0/22^22-29,
203.80.60.0/22^22-29,
210.54.136.0/22^22-29,
210.55.24.0/22^22-29,
199.212.92.0/23^23-29,
202.36.76.0/23^23-29,
202.37.240.0/23^23-29,
202.37.252.0/23^23-29,
202.174.6.0/23^23-29,
205.233.136.0/23^23-29,
210.4.212.0/23^23-29,
192.88.85.0/24^24-29,
198.32.66.0/24^24-29,
202.6.84.0/24^24-29,
202.12.70.0/24^24-29,
202.14.100.0/24^24-29,
202.21.130.0/24^24-29,
202.27.208.0/24^24-29,
202.36.45.0/24^24-29,
202.36.119.0/24^24-29,
202.36.183.0/24^24-29,
202.37.57.0/24^24-29,
202.37.73.0/24^24-29,
202.37.76.0/24^24-29,
202.37.85.0/24^24-29,
202.37.163.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.62.0/24^24-29,
202.49.159.0/24^24-29,
202.50.87.0/24^24-29,
202.50.139.0/24^24-29,
210.54.140.0/24^24-29,
210.54.211.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: deon(a)iconz.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081031
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS4770
descr: advertised to AS9560 by ICONZ - AS4770
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
210.48.0.0/17^17-29,
210.185.0.0/18^18-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.154.128.0/19^19-29,
210.54.160.0/19^19-29,
114.134.160.0/20^20-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.55.96.0/20^20-29,
202.160.48.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
203.96.16.0/20^20-29,
203.96.48.0/20^20-29,
203.96.128.0/20^20-29,
210.48.160.0/20^20-29,
210.56.32.0/20^20-29,
114.134.176.0/21^21-29,
116.90.128.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
120.138.16.0/21^21-29,
123.108.144.0/21^21-29,
192.173.16.0/21^21-29,
202.12.248.0/21^21-29,
202.37.144.0/21^21-29,
202.37.224.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.49.152.0/21^21-29,
202.50.200.0/21^21-29,
202.74.224.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
205.233.128.0/21^21-29,
210.4.208.0/21^21-29,
202.36.36.0/22^22-29,
202.37.48.0/22^22-29,
202.37.140.0/22^22-29,
202.37.200.0/22^22-29,
202.41.136.0/22^22-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.59.4.0/22^22-29,
202.89.4.0/22^22-29,
203.80.60.0/22^22-29,
210.54.136.0/22^22-29,
210.55.24.0/22^22-29,
202.6.116.0/23^23-29,
202.21.136.0/23^23-29,
202.36.44.0/23^23-29,
202.36.76.0/23^23-29,
202.36.204.0/23^23-29,
202.37.86.0/23^23-29,
202.37.240.0/23^23-29,
202.37.252.0/23^23-29,
202.49.80.0/23^23-29,
202.50.246.0/23^23-29,
202.124.106.0/23^23-29,
202.174.6.0/23^23-29,
203.84.134.0/23^23-29,
205.233.136.0/23^23-29,
210.55.182.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.100.53.0/24^24-29,
192.107.113.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.173.24.0/24^24-29,
192.195.219.0/24^24-29,
198.32.66.0/24^24-29,
198.32.71.0/24^24-29,
199.212.93.0/24^24-29,
202.6.84.0/24^24-29,
202.12.70.0/24^24-29,
202.12.91.0/24^24-29,
202.14.100.0/24^24-29,
202.20.97.0/24^24-29,
202.21.130.0/24^24-29,
202.27.83.0/24^24-29,
202.27.208.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.183.0/24^24-29,
202.36.218.0/24^24-29,
202.36.226.0/24^24-29,
202.37.57.0/24^24-29,
202.37.76.0/24^24-29,
202.37.85.0/24^24-29,
202.37.136.0/24^24-29,
202.37.163.0/24^24-29,
202.37.168.0/24^24-29,
202.37.197.0/24^24-29,
202.37.205.0/24^24-29,
202.37.232.0/24^24-29,
202.41.140.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.62.0/24^24-29,
202.49.89.0/24^24-29,
202.49.106.0/24^24-29,
202.49.249.0/24^24-29,
202.50.87.0/24^24-29,
203.97.5.0/24^24-29,
203.119.56.0/24^24-29,
205.233.243.0/24^24-29,
210.54.140.0/24^24-29,
210.54.211.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: john(a)iconz.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081124
source: NZRR
------------------------------------------------------------
