bgpreport

Network · data from 2026-11-12

AS154146 PT Global Asta Systelematika

Registry name: IDNIC-GLOBALASTA-AS-ID - PT Global Asta Systelematika, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154146, 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.
154.37.244.0/24 Invalid: maxLength Nonecovered by 154.37.244.0/22 111 16% 51
154.37.245.0/24 Invalid: maxLength Nonecovered by 154.37.244.0/22 111 16% 51
154.37.246.0/24 Invalid: maxLength Nonecovered by 154.37.244.0/22 111 16% 51
38.45.153.0/24 Valid RIR databaseARIN 673 100% 68
192.147.114.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
2001:df5:ebc0::/48 Valid RIR databaseAPNIC, RADB 636 100% 70

AS-SET

PeeringDB's irr_as_set for AS154146: AS154146:AS-GLOBALASTA. 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 (AS154146 isn't in the set, or no route object for AS154146 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 objectsAS154146 in itNot covered
AS154146:AS-GLOBALASTA APNIC 114 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 7 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength154.37.244.0/24ROA 154.37.244.0/22 AS154146 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 154.37.244.0/24.111 of 673
Route object: none154.37.244.0/24No route object for it. A route object for 154.37.244.0/22 with origin AS154146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154146 in the RIR database for the space.111 of 673
ROA: maxLength154.37.245.0/24ROA 154.37.244.0/22 AS154146 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 154.37.245.0/24.111 of 673
Route object: none154.37.245.0/24No route object for it. A route object for 154.37.244.0/22 with origin AS154146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154146 in the RIR database for the space.111 of 673
ROA: maxLength154.37.246.0/24ROA 154.37.244.0/22 AS154146 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 154.37.246.0/24.111 of 673
Route object: none154.37.246.0/24No route object for it. A route object for 154.37.244.0/22 with origin AS154146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154146 in the RIR database for the space.111 of 673

Route objects not announced

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

154.37.244.0/22ARINValid

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.