bgpreport

Network · data from 2026-11-12

AS199695 AnymHost

Registry name: ANYM-NET PT Anym Network Indonesia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199695, 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.
2a12:bec0:170::/48 No ROA Nonecovered by 2a12:bec0:170::/44 632 99% 68
2a12:bec4:1620::/48 Valid Other IRR onlyRADB 631 99% 67
103.49.130.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
109.110.188.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
163.223.227.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a12:bec0:170::/48No ROA covers it. Add a ROA for AS199695, maxLength 48.632 of 636
Route object: none2a12:bec0:170::/48No route object for it. A route object for 2a12:bec0:170::/44 with origin AS199695 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199695 in the RIR database for the space.632 of 636
Route object: RIR2a12:bec4:1620::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

2a12:bec0:170::/44RADBNo ROA
2a12:bec0:171::/48RADBNo ROA

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.