bgpreport

Network · data from 2026-11-12

AS201111 AS_FINTRAX Planet Payment Group Holdings Limited

Registry name: AS_FINTRAX Planet Payment Group Holdings Limited, IE · not in PeeringDB

7IPv4 routes 42.9% RPKI valid · 71.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
4No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS201111, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201111, 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.82.242.0/24 No ROA Other origin onlycovered by 185.82.240.0/22 671 100% 67
185.82.243.0/24 No ROA Other origin onlycovered by 185.82.240.0/22 671 100% 67
185.82.240.0/24 No ROA RIR databaseRIPE 671 100% 67
185.82.241.0/24 No ROA RIR databaseRIPE 671 100% 67
91.223.186.0/24 Valid RIR databaseRIPE 671 100% 67
185.253.204.0/22 Valid RIR databaseRIPE 671 100% 67
193.16.220.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS201111 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 8 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.82.242.0/24No ROA covers it. Add a ROA for AS201111, maxLength 24.671 of 673
Route object: none185.82.242.0/24Route objects for it name AS198949. A route object for 185.82.240.0/22 with origin AS201111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201111 in the RIR database for the space.671 of 673
ROA: none185.82.243.0/24No ROA covers it. Add a ROA for AS201111, maxLength 24.671 of 673
Route object: none185.82.243.0/24Route objects for it name AS198949. A route object for 185.82.240.0/22 with origin AS201111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201111 in the RIR database for the space.671 of 673
ROA: none185.82.240.0/24No ROA covers it. Add a ROA for AS201111, maxLength 24.671 of 673
ROA: none185.82.241.0/24No ROA covers it. Add a ROA for AS201111, maxLength 24.671 of 673

Route objects not announced

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

185.82.240.0/22RIPENo ROA
185.253.206.0/23RIPEValid

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.