This is a beta/testing instance of PeeringDB. Some features may work differently than production. Do not store data here that you intend to keep - all data will be refreshed from production at 2024-11-17 00:00:00Z
ZANOG
Organization
Also Known As
ZANOG
Long Name
ASN
328365
IRR as-set/route-set
AS-ZANOG
Route Server URL
Looking Glass URL
Network Types
Non-Profit
IPv4 Prefixes
5
IPv6 Prefixes
5
Traffic Levels
50-100Gbps
Traffic Ratios
Not Disclosed
Geographic Scope
Not Disclosed
Protocols Supported
Unicast IPv4
Multicast
IPv6
Never via route servers
Last Updated
2022-08-15T22:55:29Z
Public Peering Info Updated
2023-06-09T00:30:02Z
Peering Facility Info Updated
2023-04-13T12:40:06Z
Contact Info Updated
2020-02-05T09:33:48Z
Notes
We require peers to have a peering db entry and adequately maintain the entry to reflect current information.
We expect peers to provide us contact details via Peeringdb (either telephonic or email based) where we can address peering related issues. Such contact points should be monitored and responded to in a timely fashion.
We ask our peers to reciprocate with shortest exit (‘hot potato’) routing.
We ask peers to avoid excessive pre‐pending and de-aggregation where possible.
We expect peers to honour the ‘no-export’ BGP community sent by us.
Peers must agree never to statically route, or otherwise cause traffic, to flow towards any prefix we do not explicitly announce via BGP.
ZANOG will only peer via eBGP on public ASN’s, on public address space (we will not peer over RFC1918 address space or to a private ASN).
We expect peers to maintain a route set in a route registry of their choice, and have it listed in peeringdb, by which we will generate filters from
We expect the RPKI signing of all transmitted prefixes.
We expect peers to only announce prefixes that are legitimately assigned to them or their customers.
We expect peers to have sufficient capacity on their peering links to avoid congestion and reserve the right to de-peer any party who is consistently running congested peering circuits.
RIR Status
ok
RIR Status Updated
2024-06-26T04:47:55Z
Peering Policy Information
Peering Policy
General Policy
Open
Multiple Locations
Not Required
Ratio Requirement
No
Contract Requirement
Not Required
Health Check
Contact Information
Some of this network's contacts are hidden because they are only visible to authenticated users and you are currently not logged in.
Public Peering Exchange Points
Exchange
IPv4
ASN
IPv6
Speed
Port Location
RS Peer
BFD Support
You may filter by Exchange, ASN or Speed.
Interconnection Facilities
Facility
ASN
Country
City
You may filter by Facility, ASN, Country or City.
