bgpreport

Network · data from 2026-11-12

AS203058 TIMS

Registry name: TIMS TIMS Systemes SAS, FR · PeeringDB

8IPv4 routes 37.5% RPKI valid · 62.5% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS203058, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203058, 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.146.76.0/23 No ROA Nonecovered by 185.146.76.0/22 673 100% 67
185.146.78.0/24 No ROA Nonecovered by 185.146.76.0/22 673 100% 67
185.146.79.0/24 No ROA Nonecovered by 185.146.76.0/22 673 100% 67
2a07:4e00::/30 No ROA Nonecovered by 2a07:4e00::/29 635 100% 67
2a07:4e04::/30 No ROA Nonecovered by 2a07:4e00::/29 635 100% 67
185.146.76.0/22 No ROA RIR databaseRIPE 673 100% 67
185.209.48.0/24 No ROA RIR databaseRIPE 673 100% 67
2a07:4e00::/29 No ROA RIR databaseRIPE 635 100% 67
141.11.154.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
163.5.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.156.0/24 Valid RIR databaseRADB, RIPE 661 98% 66

AS-SET

AS203058'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 13 are in fix.csv.

  • ROA: none8
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none185.146.76.0/23No ROA covers it. Add a ROA for AS203058, maxLength 23.673 of 673
Route object: none185.146.76.0/23No route object for it. A route object for 185.146.76.0/22 with origin AS203058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203058 in the RIR database for the space.673 of 673
ROA: none185.146.78.0/24No ROA covers it. Add a ROA for AS203058, maxLength 24.673 of 673
Route object: none185.146.78.0/24No route object for it. A route object for 185.146.76.0/22 with origin AS203058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203058 in the RIR database for the space.673 of 673
ROA: none185.146.79.0/24No ROA covers it. Add a ROA for AS203058, maxLength 24.673 of 673
Route object: none185.146.79.0/24No route object for it. A route object for 185.146.76.0/22 with origin AS203058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203058 in the RIR database for the space.673 of 673
ROA: none2a07:4e00::/30No ROA covers it. Add a ROA for AS203058, maxLength 30.635 of 636
Route object: none2a07:4e00::/30No route object for it. A route object for 2a07:4e00::/29 with origin AS203058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203058 in the RIR database for the space.635 of 636
ROA: none2a07:4e04::/30No ROA covers it. Add a ROA for AS203058, maxLength 30.635 of 636
Route object: none2a07:4e04::/30No route object for it. A route object for 2a07:4e00::/29 with origin AS203058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203058 in the RIR database for the space.635 of 636
ROA: none185.146.76.0/22No ROA covers it. Add a ROA for AS203058, maxLength 22.673 of 673
ROA: none185.209.48.0/24No ROA covers it. Add a ROA for AS203058, maxLength 24.673 of 673
ROA: none2a07:4e00::/29No ROA covers it. Add a ROA for AS203058, maxLength 29.635 of 636

Route objects not announced

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