bgpreport

Network · data from 2026-11-12

AS329010 SIN

Registry name: Société d'Infrastructures Numériques (SIN) - Société d'Infrastructures Numériques (SIN), TG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329010, 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.
2c0f:4080::/32 No ROA None 604 95% 67
102.217.12.0/24 Valid None 671 100% 67

AS-SET

AS329010'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 3 are in fix.csv.

  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none2c0f:4080::/32No ROA covers it. Add a ROA for AS329010, maxLength 32.604 of 636
Route object: none2c0f:4080::/32No route object for it. Add a route object with origin AS329010 in the RIR database for the space.604 of 636
Route object: none102.217.12.0/24No route object for it. Add a route object with origin AS329010 in the RIR database for the space.671 of 673

Route objects not announced

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