bgpreport

Network · data from 2026-11-12

AS149681 Oreo Smart Access

Registry name: IDNIC-OSA-AS-ID - PT Oreo Smart Access, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149681, 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.
2401:2e60::/48 No ROA None 43 7%low visibility 33
2401:2e60:1::/48 No ROA None 43 7%low visibility 33
2401:2e60:2::/48 No ROA None 43 7%low visibility 33
103.185.40.0/24 Valid RIR databaseAPNIC, RADB 671 100% 69
103.185.41.0/24 Valid RIR databaseAPNIC, RADB 671 100% 69

AS-SET

PeeringDB's irr_as_set for AS149681: AS149681:AS-OSA. 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 (AS149681 isn't in the set, or no route object for AS149681 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 objectsAS149681 in itNot covered
AS149681:AS-OSA APNIC 113 Yes 3

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2401:2e60::/48No ROA covers it. Add a ROA for AS149681, maxLength 48.43 of 636
Route object: none2401:2e60::/48No route object for it. Add a route object with origin AS149681 in the RIR database for the space.43 of 636
ROA: none2401:2e60:1::/48No ROA covers it. Add a ROA for AS149681, maxLength 48.43 of 636
Route object: none2401:2e60:1::/48No route object for it. Add a route object with origin AS149681 in the RIR database for the space.43 of 636
ROA: none2401:2e60:2::/48No ROA covers it. Add a ROA for AS149681, maxLength 48.43 of 636
Route object: none2401:2e60:2::/48No route object for it. Add a route object with origin AS149681 in the RIR database for the space.43 of 636

Route objects not announced

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

103.185.40.0/23APNIC, RADBValid

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.