Network · data from 2026-11-12

AS59852 qotico QOTICO TELECOM SAS

Registry name: qotico QOTICO TELECOM SAS, FR · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS59852, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59852, 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.253.10.75/32	Invalid: maxLength	Nonecovered by 185.253.10.0/24	0 0%low visibility	2
185.253.10.0/24	Valid	RIR databaseRIPE	673 100%	66
2a10:b4c0::/29	Valid	RIR databaseRIPE	634 100%	69

185.253.10.75/32

Invalid: maxLength

Nonecovered by 185.253.10.0/24

0 0%low visibility

185.253.10.0/24

Valid

RIR databaseRIPE

673 100%

2a10:b4c0::/29

Valid

RIR databaseRIPE

634 100%

AS-SET

AS59852 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 2 are in fix.csv.

ROA: maxLength1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	185.253.10.75/32	ROA 185.253.10.0/24 AS59852 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.253.10.75/32.	0 of 673
Route object: none	185.253.10.75/32	No route object for it. A route object for 185.253.10.0/24 with origin AS59852 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59852 in the RIR database for the space.	0 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

185.253.10.75/32

ROA 185.253.10.0/24 AS59852 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.253.10.75/32.

0 of 673

Route object: none

185.253.10.75/32

No route object for it. A route object for 185.253.10.0/24 with origin AS59852 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59852 in the RIR database for the space.

0 of 673

Route objects not announced

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