bgpreport

Network · data from 2026-11-12

AS199528 ORG-PA1509-RIPE PE "AVUBIS-INTERTAINMENT"

Registry name: ORG-PA1509-RIPE PE "AVUBIS-INTERTAINMENT", UZ · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
0No 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 AS199528, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199528, 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.

95.46.5.0/25 Invalid: maxLength Nonecovered by 95.46.5.0/24 1 0%low visibility 1
95.46.5.0/24 Valid RIR databaseRIPE 673 100% 68

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength95.46.5.0/25ROA 95.46.5.0/24 AS199528 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 95.46.5.0/25.1 of 673
Route object: none95.46.5.0/25No route object for it. A route object for 95.46.5.0/24 with origin AS199528 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS199528 in the RIR database for the space.1 of 673

Route objects not announced

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