bgpreport

Network · data from 2026-11-12

AS137267 CBROS Technologies

Registry name: CTL-AS-AP - Sharp ICT, NZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137267, 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.

2400:1360::/32 No ROA Other IRR onlyRADB 636 100% 69
103.106.110.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 68
103.106.111.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 68
2001:df3:a300::/48 No ROA RIR databaseAPNIC, RADB 636 100% 69
203.27.18.0/24 Valid RIR databaseAPNIC 671 100% 68
203.33.188.0/24 Valid RIR databaseAPNIC 670 100% 67
2400:1360::/34 Valid RIR databaseAPNIC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS137267: AS-CBROS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS137267 isn't in the set, or no route object for AS137267 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS137267 in itNot covered
AS-CBROS APNIC 2212 Yes 0

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: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2400:1360::/32No ROA covers it. Add a ROA for AS137267, maxLength 32.636 of 636
Route object: RIR2400:1360::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none103.106.110.0/24No ROA covers it. Add a ROA for AS137267, maxLength 24.671 of 673
ROA: none103.106.111.0/24No ROA covers it. Add a ROA for AS137267, maxLength 24.671 of 673
ROA: none2001:df3:a300::/48No ROA covers it. Add a ROA for AS137267, maxLength 48.636 of 636

Route objects not announced

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

103.106.110.0/23APNIC, RADBNo 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.