bgpreport

Network · data from 2026-11-12

AS17889 Intraceptives

Registry name: INTRACEPTIVES-AU-AS-AP - Intraceptives Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17889, 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.21.21.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.22.72.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
116.212.64.0/21 No ROA Other IRR onlyNTTCOM 671 100% 67

AS-SET

AS17889's PeeringDB record names no 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 23 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none203.21.21.0/24No ROA covers it. Add a ROA for AS17889, maxLength 24.673 of 673
Route object: RIR203.21.21.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.22.72.0/23No ROA covers it. Add a ROA for AS17889, maxLength 23.673 of 673
Route object: RIR203.22.72.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.212.64.0/21No ROA covers it. Add a ROA for AS17889, maxLength 21.671 of 673
Route object: RIR116.212.64.0/21Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS17889 whose prefix no peer sees AS17889 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.58.32.0/24NTTCOM, RADBNo ROA
116.212.64.0/22NTTCOMNo ROA
116.212.64.0/23NTTCOMNo ROA
116.212.64.0/24NTTCOMNo ROA
116.212.65.0/24NTTCOMNo ROA
116.212.66.0/23NTTCOMNo ROA
116.212.66.0/24NTTCOMNo ROA
116.212.67.0/24NTTCOMNo ROA
116.212.68.0/22NTTCOMNo ROA
116.212.68.0/23NTTCOMNo ROA
116.212.68.0/24NTTCOMNo ROA
116.212.69.0/24NTTCOMNo ROA
116.212.70.0/23NTTCOMNo ROA
116.212.70.0/24NTTCOMNo ROA
116.212.71.0/24NTTCOMNo ROA
203.22.72.0/24NTTCOMNo ROA
203.22.73.0/24NTTCOMNo ROA

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.