bgpreport

Network · data from 2026-11-12

AS197352 Tinext SA

Registry name: TINEXT Tinext Cloud SA, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197352, 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.
46.21.24.0/22 No ROA RIR databaseRIPE 671 100% 67
185.94.148.0/22 No ROA RIR databaseRIPE 671 100% 67
185.181.204.0/22 No ROA RIR databaseRIPE 671 100% 67
194.11.217.0/24 No ROA RIR databaseRIPE 671 100% 67
195.72.40.0/22 No ROA RIR databaseRIPE 671 100% 67
2a0a:d280::/29 No ROA RIR databaseRIPE 634 100% 68
194.9.55.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS197352'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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none46.21.24.0/22No ROA covers it. Add a ROA for AS197352, maxLength 22.671 of 673
ROA: none185.94.148.0/22No ROA covers it. Add a ROA for AS197352, maxLength 22.671 of 673
ROA: none185.181.204.0/22No ROA covers it. Add a ROA for AS197352, maxLength 22.671 of 673
ROA: none194.11.217.0/24No ROA covers it. Add a ROA for AS197352, maxLength 24.671 of 673
ROA: none195.72.40.0/22No ROA covers it. Add a ROA for AS197352, maxLength 22.671 of 673
ROA: none2a0a:d280::/29No ROA covers it. Add a ROA for AS197352, maxLength 29.634 of 636

Route objects not announced

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