bgpreport

Network · data from 2026-11-12

AS138023 Creation Online

Registry name: CREATION-AS-AP - Creation Online, BD · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS138023, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138023, 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.
103.137.109.0/24 Valid RIR databaseAPNIC 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS138023: AS138023:AS-ALL. 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 (AS138023 isn't in the set, or no route object for AS138023 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 objectsAS138023 in itNot covered
AS138023:AS-ALL APNIC 213 No 1

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.

  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS138023:AS-ALLAS138023 isn't in AS138023:AS-ALL (APNIC) once expanded. Add AS138023 to it.

Route objects not announced

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

2001:df6:700::/48APNICValid

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.