bgpreport

Network · data from 2026-11-12

AS210154 BG-GIGALAN-EM GIGALAN EM Ltd.

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210154, 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.22.120/32 Invalid: maxLength Nonecovered by 151.237.22.0/24 3 0%low visibility 6
151.237.22.121/32 Invalid: maxLength Nonecovered by 151.237.22.0/24 3 0%low visibility 6
94.236.203.0/24 No ROA RIR databaseRIPE 269 40% 61
151.237.20.0/24 Valid RIR databaseRIPE 673 100% 66
151.237.21.0/24 Valid RIR databaseRIPE 673 100% 66
151.237.22.0/24 Valid RIR databaseRIPE 673 100% 66
151.237.32.0/24 Valid RIR databaseRIPE 673 100% 66
46.254.135.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS210154 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: maxLength2
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: maxLength151.237.22.120/32ROA 151.237.22.0/24 AS210154 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 151.237.22.120/32.3 of 673
Route object: none151.237.22.120/32No route object for it. A route object for 151.237.22.0/24 with origin AS210154 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS210154 in the RIR database for the space.3 of 673
ROA: maxLength151.237.22.121/32ROA 151.237.22.0/24 AS210154 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 151.237.22.121/32.3 of 673
Route object: none151.237.22.121/32No route object for it. A route object for 151.237.22.0/24 with origin AS210154 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS210154 in the RIR database for the space.3 of 673
ROA: none94.236.203.0/24No ROA covers it. Add a ROA for AS210154, maxLength 24.269 of 673

Route objects not announced

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