bgpreport

Network · data from 2026-11-12

AS207747 IAAS365 IAAS 365, SL

Registry name: IAAS365 IAAS 365, SL, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207747, 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.

45.95.196.0/22 No ROA RIR databaseRIPE 673 100% 67
45.95.196.0/24 No ROA RIR databaseRIPE 672 100% 67
45.95.198.0/24 No ROA RIR databaseRIPE 672 100% 67
2a0e:38c0::/32 No ROA RIR databaseRIPE 635 100% 67
2a0e:38c0:100::/40 No ROA RIR databaseRIPE 635 100% 67
2a0e:38c0:200::/40 No ROA RIR databaseRIPE 635 100% 67
195.143.125.0/24 Valid None 673 100% 67

AS-SET

AS207747 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 10 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.95.196.0/22No ROA covers it. Add a ROA for AS207747, maxLength 22.673 of 673
ROA: none45.95.196.0/24No ROA covers it. Add a ROA for AS207747, maxLength 24.672 of 673
ROA: none45.95.198.0/24No ROA covers it. Add a ROA for AS207747, maxLength 24.672 of 673
ROA: none2a0e:38c0::/32No ROA covers it. Add a ROA for AS207747, maxLength 32.635 of 636
ROA: none2a0e:38c0:100::/40No ROA covers it. Add a ROA for AS207747, maxLength 40.635 of 636
ROA: none2a0e:38c0:200::/40No ROA covers it. Add a ROA for AS207747, maxLength 40.635 of 636
Route object: none195.143.125.0/24No route object for it. Add a route object with origin AS207747 in the RIR database for the space.673 of 673

Route objects not announced

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

45.95.197.0/24RIPENo ROA
45.95.199.0/24RIPENo ROA
2a0e:38c0::/29RIPENo 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.