bgpreport

Network · data from 2026-11-12

AS141400 COMCARE-AS-AP - COMCARE

Registry name: COMCARE-AS-AP - COMCARE, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141400, 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.
163.233.128.0/20 Invalid: maxLength Nonecovered by 163.233.0.0/16 15 2%low visibility 7
163.233.0.0/16 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS141400 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 2 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength163.233.128.0/20ROA 163.233.0.0/16 AS141400 has maxLength 16; the route is a /20. Raise the maxLength, or add a ROA for 163.233.128.0/20.15 of 673
Route object: none163.233.128.0/20No route object for it. A route object for 163.233.0.0/16 with origin AS141400 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141400 in the RIR database for the space.15 of 673

Route objects not announced

Every route object with origin AS141400 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.