bgpreport

Network · data from 2026-11-12

AS133809 ARTORIUS

Registry name: ARTORIUS-AS-ID - PT. Artorius Telemetri Sentosa, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133809, 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:6f20::/48 Valid Nonecovered by 2400:6f20::/32 34 5%low visibility 28
2400:6f20:4::/48 Valid Nonecovered by 2400:6f20::/32 34 5%low visibility 28
2400:6f20:5::/48 Valid Nonecovered by 2400:6f20::/32 34 5%low visibility 28
2400:6f20:6::/48 Valid Nonecovered by 2400:6f20::/32 34 5%low visibility 28
2400:6f20:1::/48 Valid Nonecovered by 2400:6f20::/32 1 0%low visibility 1
103.50.128.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.50.128.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
103.50.129.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
103.50.130.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
103.50.131.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70

AS-SET

AS133809's PeeringDB record names no AS-SET.

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

  • Route object: none5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2400:6f20::/48No route object for it. A route object for 2400:6f20::/32 with origin AS133809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133809 in the RIR database for the space.34 of 636
Route object: none2400:6f20:4::/48No route object for it. A route object for 2400:6f20::/32 with origin AS133809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133809 in the RIR database for the space.34 of 636
Route object: none2400:6f20:5::/48No route object for it. A route object for 2400:6f20::/32 with origin AS133809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133809 in the RIR database for the space.34 of 636
Route object: none2400:6f20:6::/48No route object for it. A route object for 2400:6f20::/32 with origin AS133809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133809 in the RIR database for the space.34 of 636
Route object: none2400:6f20:1::/48No route object for it. A route object for 2400:6f20::/32 with origin AS133809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133809 in the RIR database for the space.1 of 636

Route objects not announced

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

103.50.128.0/23RADBValid
103.50.130.0/23RADBValid
202.51.58.0/23APNICInvalid: origin
2400:6f20::/32RADBValid

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.