bgpreport

Network · data from 2026-11-12

AS134673 GISBORNE-AS-AP - Gisborne/Eastcoast Internet Services

Registry name: GISBORNE-AS-AP - Gisborne/Eastcoast Internet Services, NZ · not in PeeringDB

8IPv4 routes 62.5% RPKI valid · 62.5% with a route object
0IPv6 routes
3RPKI invalid 3 origin · 0 maxLength
0No ROA 3 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS134673, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134673, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
203.25.187.0/24 Invalid: origin Other origin only 41 6%low visibility 26
203.189.24.0/24 Invalid: origin Other origin only 41 6%low visibility 26
203.190.217.0/24 Invalid: origin Other origin only 41 6%low visibility 26
103.209.224.0/22 Valid RIR databaseAPNIC 673 100% 68
202.27.212.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.27.247.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.49.183.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.18.59.0/24 Valid RIR databaseAPNIC 673 100% 68

AS-SET

AS134673 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • ROA: origin3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin203.25.187.0/24ROAs covering it name AS9303, not AS134673. If AS134673 should announce it, add a ROA for AS134673.41 of 673
Route object: none203.25.187.0/24Route objects for it name AS9303. Add a route object with origin AS134673 in the RIR database for the space.41 of 673
ROA: origin203.189.24.0/24ROAs covering it name AS9303, not AS134673. If AS134673 should announce it, add a ROA for AS134673.41 of 673
Route object: none203.189.24.0/24Route objects for it name AS9303. Add a route object with origin AS134673 in the RIR database for the space.41 of 673
ROA: origin203.190.217.0/24ROAs covering it name AS9303, not AS134673. If AS134673 should announce it, add a ROA for AS134673.41 of 673
Route object: none203.190.217.0/24Route objects for it name AS9303. Add a route object with origin AS134673 in the RIR database for the space.41 of 673

Route objects not announced

Every route object with origin AS134673 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.