bgpreport

Network · data from 2026-11-12

AS152089 IDNIC-SINGKINET-AS-ID - PT Singki Media Telekomunikasi

Registry name: IDNIC-SINGKINET-AS-ID - PT Singki Media Telekomunikasi, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152089, 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.
141.11.237.0/24 Invalid: origin Other origin only 6 1%low visibility 5
157.10.156.0/24 No ROA Other IRR onlyRADB 671 100% 68
2a13:9500:168::/48 Valid RIR databaseRIPE 633 100% 68

AS-SET

AS152089 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin141.11.237.0/24ROAs covering it name AS198831, not AS152089. If AS152089 should announce it, add a ROA for AS152089.6 of 673
Route object: none141.11.237.0/24Route objects for it name AS198831. Add a route object with origin AS152089 in the RIR database for the space.6 of 673
ROA: none157.10.156.0/24No ROA covers it. Add a ROA for AS152089, maxLength 24.671 of 673
Route object: RIR157.10.156.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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