bgpreport

Network · data from 2026-11-12

AS212782 ThreeUK Circles MVNE International B.V.

Registry name: ThreeUK Circles MVNE International B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212782, 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.
2a0a:60c1:2::/48 No ROA None 634 100% 67
185.222.225.0/30 No ROA Nonecovered by 185.222.225.0/24 1 0%low visibility 1
185.222.225.10/31 No ROA Nonecovered by 185.222.225.0/24 1 0%low visibility 1
185.222.225.13/32 No ROA Nonecovered by 185.222.225.0/24 1 0%low visibility 1
185.222.225.32/29 No ROA Nonecovered by 185.222.225.0/24 1 0%low visibility 1
185.222.225.0/24 No ROA RIR databaseRIPE 671 100% 66

AS-SET

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

  • ROA: none6
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:60c1:2::/48No ROA covers it. Add a ROA for AS212782, maxLength 48.634 of 636
Route object: none2a0a:60c1:2::/48No route object for it. Add a route object with origin AS212782 in the RIR database for the space.634 of 636
ROA: none185.222.225.0/30No ROA covers it. Add a ROA for AS212782, maxLength 30.1 of 673
Route object: none185.222.225.0/30No route object for it. A route object for 185.222.225.0/24 with origin AS212782 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212782 in the RIR database for the space.1 of 673
ROA: none185.222.225.10/31No ROA covers it. Add a ROA for AS212782, maxLength 31.1 of 673
Route object: none185.222.225.10/31No route object for it. A route object for 185.222.225.0/24 with origin AS212782 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212782 in the RIR database for the space.1 of 673
ROA: none185.222.225.13/32No ROA covers it. Add a ROA for AS212782, maxLength 32.1 of 673
Route object: none185.222.225.13/32No route object for it. A route object for 185.222.225.0/24 with origin AS212782 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212782 in the RIR database for the space.1 of 673
ROA: none185.222.225.32/29No ROA covers it. Add a ROA for AS212782, maxLength 29.1 of 673
Route object: none185.222.225.32/29No route object for it. A route object for 185.222.225.0/24 with origin AS212782 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212782 in the RIR database for the space.1 of 673
ROA: none185.222.225.0/24No ROA covers it. Add a ROA for AS212782, maxLength 24.671 of 673

Route objects not announced

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