bgpreport

Network · data from 2026-11-12

AS52157 NONEAS-AS NEAS ENERGI TELEKOM AS

Registry name: NONEAS-AS NEAS ENERGI TELEKOM AS, NO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52157, 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.
5.100.188.0/22 Valid RIR databaseRIPE 673 100% 67
93.89.112.0/20 Valid RIR databaseRIPE 673 100% 67
185.193.92.0/22 Valid RIR databaseRIPE 673 100% 67
185.209.224.0/22 Valid RIR databaseRIPE 673 100% 66
185.237.36.0/22 Valid RIR databaseRIPE 673 100% 66
2a02:25e8::/29 Valid RIR databaseRIPE 634 100% 67
2a03:ba02::/32 Valid RIR databaseRIPE 3 0%low visibility 2

AS-SET

AS52157 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.

  • Route object: not announced2

Route objects not announced

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

2a03:ba00::/32RIPEValid
2a03:ba01::/32RIPEValid

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.