bgpreport

Network · data from 2026-11-12

AS57546 Bul Ins

Registry name: BULINS-AS Bul Ins AD, BG · PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 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 AS57546, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57546, 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.
212.56.4.0/23 Invalid: origin None 22 3%low visibility 17
212.56.4.0/24 Valid RIR databaseRIPE 673 100% 67
212.56.5.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin212.56.4.0/23ROAs covering it name AS3257, not AS57546. If AS57546 should announce it, add a ROA for AS57546.22 of 673
Route object: none212.56.4.0/23No route object for it. Add a route object with origin AS57546 in the RIR database for the space.22 of 673

Route objects not announced

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