bgpreport

Network · data from 2026-11-12

AS202825 neartel NEAR TELECOM S.L.

Registry name: neartel NEAR TELECOM S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202825, 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.
185.153.116.0/24 No ROA RIR databaseRIPE 673 100% 67
185.153.117.0/24 No ROA RIR databaseRIPE 673 100% 67
185.153.118.0/24 No ROA RIR databaseRIPE 673 100% 67
185.153.119.0/24 No ROA RIR databaseRIPE 673 100% 67
193.46.176.0/24 No ROA RIR databaseRIPE 673 100% 67
193.46.177.0/24 No ROA RIR databaseRIPE 673 100% 67
193.46.178.0/24 No ROA RIR databaseRIPE 673 100% 67
193.46.179.0/24 No ROA RIR databaseRIPE 673 100% 67
2a0c:8d40::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none9
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none185.153.116.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none185.153.117.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none185.153.118.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none185.153.119.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none193.46.176.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none193.46.177.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none193.46.178.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none193.46.179.0/24No ROA covers it. Add a ROA for AS202825, maxLength 24.673 of 673
ROA: none2a0c:8d40::/29No ROA covers it. Add a ROA for AS202825, maxLength 29.634 of 636

Route objects not announced

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

185.153.116.0/22RIPENo ROA
193.46.176.0/22RIPENo ROA
193.46.176.0/23RIPENo ROA
193.46.178.0/23RIPENo ROA
2a0c:8d40::/32RIPENo ROA
2a0c:8d41::/32RIPENo ROA
2a0c:8d42::/32RIPENo ROA
2a0c:8d43::/32RIPENo ROA
2a0c:8d44::/32RIPENo ROA
2a0c:8d45::/32RIPENo ROA
2a0c:8d46::/32RIPENo ROA
2a0c:8d47::/32RIPENo ROA

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.