bgpreport

Network · data from 2026-11-12

AS201105 INTERSUR

Registry name: INTERSUR WIFI INTERSUR S.L., ES · PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS201105, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201105, 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.198.180.0/22 No ROA RIR databaseRIPE 672 100% 67
185.83.160.0/22 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS201105's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none185.198.180.0/22No ROA covers it. Add a ROA for AS201105, maxLength 22.672 of 673

Route objects not announced

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

82.129.0.0/24RIPENo ROA
82.129.1.0/24RIPENo ROA
82.129.2.0/24RIPENo ROA
82.129.3.0/24RIPENo ROA
185.83.160.0/24RIPEInvalid: maxLength
185.83.161.0/24RIPEInvalid: maxLength
185.83.162.0/24RIPEInvalid: maxLength
185.83.163.0/24RIPEInvalid: maxLength
185.198.180.0/24RIPENo ROA
185.198.181.0/24RIPENo ROA
185.198.182.0/24RIPENo ROA
185.198.183.0/24RIPENo 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.