bgpreport

Network · data from 2026-11-12

AS8734 DZI-BG DZI Obshto Zastrahovane EAD

Registry name: DZI-BG DZI Obshto Zastrahovane EAD, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8734, 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.
94.156.221.97/32 Invalid: origin None 2 0%low visibility 2
94.156.221.104/32 Invalid: origin None 2 0%low visibility 2
87.120.140.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
95.43.206.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS8734 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 5 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin94.156.221.97/32ROAs covering it name AS34224, not AS8734. If AS8734 should announce it, add a ROA for AS8734.2 of 673
Route object: none94.156.221.97/32No route object for it. Add a route object with origin AS8734 in the RIR database for the space.2 of 673
ROA: origin94.156.221.104/32ROAs covering it name AS34224, not AS8734. If AS8734 should announce it, add a ROA for AS8734.2 of 673
Route object: none94.156.221.104/32No route object for it. Add a route object with origin AS8734 in the RIR database for the space.2 of 673

Route objects not announced

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

193.245.25.0/24RIPENo 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.