bgpreport

Network · data from 2026-11-12

AS208586 ES-NEOTEL-AS Neotel 2000 S.L

Registry name: ES-NEOTEL-AS Neotel 2000 S.L, ES · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS208586, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208586, 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.
192.168.10.122/32 bogon No ROA None 1 0%low visibility 1
45.93.192.0/22 No ROA RIR databaseRIPE 673 100% 67
185.96.232.0/23 No ROA RIR databaseRIPE 673 100% 67

AS-SET

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

  • Bogon prefix1
  • ROA: none2
ChangePrefix or setDetailFull-table peers
Bogon prefix192.168.10.122/32In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
ROA: none45.93.192.0/22No ROA covers it. Add a ROA for AS208586, maxLength 22.673 of 673
ROA: none185.96.232.0/23No ROA covers it. Add a ROA for AS208586, maxLength 23.673 of 673

Route objects not announced

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