bgpreport

Network · data from 2026-11-12

AS206886 QUAD PLAY BATT

Registry name: QPB CYBERMAN INFORMATICA Y COMUNICACIONES, SRLL, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206886, 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.
2a0b:d00:1::/48 No ROA Nonecovered by 2a0b:d00::/29 2 0%low visibility 2
2a0b:d00:2::/48 No ROA Nonecovered by 2a0b:d00::/29 2 0%low visibility 2
185.172.96.0/24 Valid Nonecovered by 185.172.96.0/22 4 1%low visibility 3
185.172.97.0/24 Valid Nonecovered by 185.172.96.0/22 4 1%low visibility 3
185.172.98.0/24 Valid Nonecovered by 185.172.96.0/22 4 1%low visibility 3
185.172.99.0/24 Valid Nonecovered by 185.172.96.0/22 4 1%low visibility 3
185.172.96.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS206886'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 9 are in fix.csv.

  • ROA: none2
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0b:d00:1::/48No ROA covers it. Add a ROA for AS206886, maxLength 48.2 of 636
Route object: none2a0b:d00:1::/48No route object for it. A route object for 2a0b:d00::/29 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.2 of 636
ROA: none2a0b:d00:2::/48No ROA covers it. Add a ROA for AS206886, maxLength 48.2 of 636
Route object: none2a0b:d00:2::/48No route object for it. A route object for 2a0b:d00::/29 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.2 of 636
Route object: none185.172.96.0/24No route object for it. A route object for 185.172.96.0/22 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.4 of 673
Route object: none185.172.97.0/24No route object for it. A route object for 185.172.96.0/22 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.4 of 673
Route object: none185.172.98.0/24No route object for it. A route object for 185.172.96.0/22 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.4 of 673
Route object: none185.172.99.0/24No route object for it. A route object for 185.172.96.0/22 with origin AS206886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206886 in the RIR database for the space.4 of 673

Route objects not announced

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

2a0b:d00::/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.