bgpreport

Network · data from 2026-11-12

AS42459 Fiber Optics Bulgaria

Registry name: FOBUL Fiber Optics Bulgaria OOD, BG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42459, 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.45.67.11/32 Valid Nonecovered by 212.45.67.0/24 2 0%low visibility 6
79.134.48.0/20 Valid RIR databaseRIPE 673 100% 66
193.32.0.0/23 Valid RIR databaseRIPE 673 100% 66
193.32.4.0/23 Valid RIR databaseRIPE 673 100% 66
212.45.64.0/20 Valid RIR databaseRIPE 673 100% 66
212.45.67.0/24 Valid RIR databaseRIPE 673 100% 66
2a02:2660::/32 Valid RIR databaseRIPE 635 100% 69
79.134.56.0/21 Valid RIR databaseRIPE 403 60% 61
212.45.64.0/21 Valid RIR databaseRIPE 403 60% 61
212.45.72.0/21 Valid RIR databaseRIPE 403 60% 61

AS-SET

PeeringDB's irr_as_set for AS42459: AS-FOBUL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS42459 isn't in the set, or no route object for AS42459 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS42459 in itNot covered
AS-FOBUL RIPE 71109 Yes 1

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

  • Route object: none1
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
Route object: none212.45.67.11/32No route object for it. A route object for 212.45.67.0/24 with origin AS42459 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS42459 in the RIR database for the space.2 of 673

Route objects not announced

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

79.134.48.0/21RIPEValid
79.134.48.0/24RIPEValid
79.134.49.0/24RIPEValid
79.134.50.0/24RIPEValid
79.134.51.0/24RIPEValid
79.134.52.0/24RIPEValid
79.134.53.0/24RIPEValid
79.134.54.0/24RIPEValid
79.134.55.0/24RIPEValid
79.134.56.0/24RIPEValid
79.134.57.0/24RIPEValid
79.134.58.0/24RIPEValid
79.134.59.0/24RIPEValid
79.134.60.0/24RIPEValid
185.148.60.0/22RIPENo ROA
212.45.64.0/24RIPEValid
212.45.65.0/24RIPEValid
212.45.66.0/24RIPEValid
212.45.68.0/24RIPEValid
212.45.70.0/24RIPEValid
212.45.71.0/24RIPEValid
212.45.72.0/24RIPEValid
212.45.73.0/24RIPEValid
212.45.74.0/24RIPEValid
212.45.75.0/24RIPEValid
212.45.76.0/24RIPEValid
212.45.77.0/24RIPEValid
212.45.78.0/24RIPEValid
212.45.79.0/24RIPEValid

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.