bgpreport

Network · data from 2026-11-12

AS202439 BG-NETCOM NETCOM Ltd.

Registry name: BG-NETCOM NETCOM Ltd., BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202439, 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.
151.237.138.24/32 Invalid: maxLength Nonecovered by 151.237.138.0/23 3 0%low visibility 6
151.237.138.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength151.237.138.24/32ROA 151.237.138.0/23 AS202439 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 151.237.138.24/32.3 of 673
Route object: none151.237.138.24/32No route object for it. A route object for 151.237.138.0/23 with origin AS202439 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202439 in the RIR database for the space.3 of 673

Route objects not announced

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