bgpreport

Network · data from 2026-11-12

AS45723 Omadata Indonesia

Registry name: OMADATA-AS-ID - Omadata Indonesia, PT, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45723, 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.
2403:1a00:4::/47 Valid None 636 100% 69
103.28.81.0/24 Valid Nonecovered by 103.28.80.0/22 2 0%low visibility 2
103.28.82.0/24 Valid Nonecovered by 103.28.80.0/22 2 0%low visibility 2
103.28.83.0/24 Valid Nonecovered by 103.28.80.0/22 2 0%low visibility 2
103.28.80.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
202.1.236.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68
103.28.80.0/22 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS45723: AS45723:AS-OMADATA. 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 (AS45723 isn't in the set, or no route object for AS45723 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 objectsAS45723 in itNot covered
AS45723:AS-OMADATA In no IRR database read today.

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.

  • Route object: none4
  • Route object: RIR1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2403:1a00:4::/47No route object for it. Add a route object with origin AS45723 in the RIR database for the space.636 of 636
Route object: none103.28.81.0/24No route object for it. A route object for 103.28.80.0/22 with origin AS45723 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45723 in the RIR database for the space.2 of 673
Route object: none103.28.82.0/24No route object for it. A route object for 103.28.80.0/22 with origin AS45723 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45723 in the RIR database for the space.2 of 673
Route object: none103.28.83.0/24No route object for it. A route object for 103.28.80.0/22 with origin AS45723 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45723 in the RIR database for the space.2 of 673
Route object: RIR103.28.80.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS45723:AS-OMADATAPeeringDB names AS45723:AS-OMADATA; no IRR database read has it.

Route objects not announced

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