bgpreport

Network · data from 2026-11-12

AS43205 Vivacom Bulgaria EAD-Bulsatcom

Registry name: BULSATCOM-BG-AS Vivacom Bulgaria EAD, BG · PeeringDB

2IPv4 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
1Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS43205, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43205, 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.
46.40.75.0/24 Valid RIR databaseRIPE 672 100% 66
46.237.64.0/18 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

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

  • Route object: not announced7

Route objects not announced

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

46.40.64.0/18RIPEValid
46.47.64.0/18RIPEValid
91.139.128.0/17RIPEValid
185.4.80.0/22RIPEValid
206.3.160.0/20RIPE-NONAUTHNo ROA
206.3.176.0/21RIPE-NONAUTHNo ROA
212.43.32.0/19RIPEInvalid: origin

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.