bgpreport

Network · data from 2026-11-12

AS154123 PT Rayunet Broadcast Solution

Registry name: IDNIC-RAYUNET-AS-ID - PT Rayunet Broadcast Solution, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154123, 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.
79.175.83.0/24 Invalid: origin Other origin only 1 0%low visibility 1
163.52.215.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.188.80.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
38.130.253.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.143.3.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.190.148.0/24 Valid RIR databaseARIN 671 100% 67
38.190.149.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.246.178.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.246.196.0/24 Valid RIR databaseARIN 671 100% 67
154.51.246.0/24 Valid RIR databaseARIN, RADB 670 100% 67
38.131.242.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS154123'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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin79.175.83.0/24ROAs covering it name AS202828, not AS154123. If AS154123 should announce it, add a ROA for AS154123.1 of 673
Route object: none79.175.83.0/24Route objects for it name AS202828. Add a route object with origin AS154123 in the RIR database for the space.1 of 673

Route objects not announced

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

38.190.148.0/23ARINValid
2001:df5:eec0::/48APNIC, RADBValid

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.