bgpreport

Network · data from 2026-11-12

AS25076 ISTARLINK-AS KTV Istar Ltd.

Registry name: ISTARLINK-AS KTV Istar Ltd., BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25076, 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.134.48.0/21 Valid RIR databaseRIPE 403 60% 61

AS-SET

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

  • Route object: not announced13

Route objects not announced

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

79.134.48.0/20RIPEInvalid: origin
79.134.58.0/23RIPEValid
185.148.60.0/22RIPENo ROA
212.45.64.0/20RIPEInvalid: origin
212.45.64.0/21RIPEInvalid: origin
212.45.64.0/24RIPEInvalid: origin
212.45.70.0/23RIPEInvalid: origin
212.45.72.0/23RIPEValid
212.45.74.0/24RIPEValid
212.45.75.0/24RIPEValid
212.45.76.0/22RIPEValid
213.16.51.0/24RIPEInvalid: origin
2a07:5d80::/29RIPENo 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.