bgpreport

Network · data from 2026-11-12

AS60230 Neterra Neterra Ltd.

Registry name: Neterra Neterra Ltd., BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60230, 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.
194.40.251.0/24 No ROA RIR databaseRIPE 109 16% 40
2a00:1728:a::/48 Valid Other origin only 634 100% 69
31.13.244.99/32 Valid Nonecovered by 31.13.244.0/24 5 1%low visibility 9
31.13.244.0/24 Valid RIR databaseRIPE 478 71% 62

AS-SET

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

  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none194.40.251.0/24No ROA covers it. Add a ROA for AS60230, maxLength 24.109 of 673
Route object: none2a00:1728:a::/48Route objects for it name AS57463. Add a route object with origin AS60230 in the RIR database for the space.634 of 636
Route object: none31.13.244.99/32No route object for it. A route object for 31.13.244.0/24 with origin AS60230 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60230 in the RIR database for the space.5 of 673

Route objects not announced

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