bgpreport

Network · data from 2026-11-12

AS199544 Remote24 AB

Registry name: REMOTE24-AS Remote24 AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199544, 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.
2a03:7ec0:ced::/48 No ROA Nonecovered by 2a03:7ec0::/32 635 100% 67
185.14.240.0/24 Valid Nonecovered by 185.14.240.0/22 673 100% 67
185.14.241.0/24 Valid Nonecovered by 185.14.240.0/22 673 100% 67
185.14.243.0/24 Valid Nonecovered by 185.14.240.0/22 673 100% 67
2a03:7ec0:3000::/40 Valid Nonecovered by 2a03:7ec0::/32 635 100% 67
2a03:7ec0:3100::/40 Valid Nonecovered by 2a03:7ec0::/32 635 100% 67
2a03:7ec0:3100::/48 Valid Nonecovered by 2a03:7ec0::/32 635 100% 67
2a03:7ec0:31ff::/48 Valid Nonecovered by 2a03:7ec0::/32 635 100% 67
91.239.255.0/24 Valid RIR databaseRIPE 673 100% 67
2001:67c:3c::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS199544'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 11 are in fix.csv.

  • ROA: none1
  • Route object: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a03:7ec0:ced::/48No ROA covers it. Add a ROA for AS199544, maxLength 48.635 of 636
Route object: none2a03:7ec0:ced::/48No route object for it. A route object for 2a03:7ec0::/32 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.635 of 636
Route object: none185.14.240.0/24No route object for it. A route object for 185.14.240.0/22 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.673 of 673
Route object: none185.14.241.0/24No route object for it. A route object for 185.14.240.0/22 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.673 of 673
Route object: none185.14.243.0/24No route object for it. A route object for 185.14.240.0/22 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.673 of 673
Route object: none2a03:7ec0:3000::/40No route object for it. A route object for 2a03:7ec0::/32 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.635 of 636
Route object: none2a03:7ec0:3100::/40No route object for it. A route object for 2a03:7ec0::/32 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.635 of 636
Route object: none2a03:7ec0:3100::/48No route object for it. A route object for 2a03:7ec0::/32 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.635 of 636
Route object: none2a03:7ec0:31ff::/48No route object for it. A route object for 2a03:7ec0::/32 with origin AS199544 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199544 in the RIR database for the space.635 of 636

Route objects not announced

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

185.14.240.0/22RIPENo ROA
2a03:7ec0::/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.