bgpreport

Network · data from 2026-11-12

AS214961 STELLARGROUPSAS Stellar Group SAS

Registry name: STELLARGROUPSAS Stellar Group SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214961, 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.
199.104.63.250/32 Invalid: maxLength Nonecovered by 199.104.63.0/24 1 0%low visibility 1
2a10:4646:700::/48 Valid Nonecovered by 2a10:4646:700::/44 634 100% 69
94.154.32.0/24 Valid RIR databaseRIPE 672 100% 67
104.239.66.0/24 Valid RIR databaseRIPE 672 100% 67
195.177.94.0/24 Valid RIR databaseRIPE 672 100% 67
199.104.63.0/24 Valid RIR databaseRIPE 672 100% 67
217.217.97.0/24 Valid RIR databaseRIPE 672 100% 67
45.141.21.0/24 Valid RIR databaseRIPE 671 100% 66
77.73.20.0/24 Valid RIR databaseRIPE 671 100% 67
104.249.10.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS214961 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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength199.104.63.250/32ROA 199.104.63.0/24 AS214961 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 199.104.63.250/32.1 of 673
Route object: none199.104.63.250/32No route object for it. A route object for 199.104.63.0/24 with origin AS214961 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214961 in the RIR database for the space.1 of 673
Route object: none2a10:4646:700::/48No route object for it. A route object for 2a10:4646:700::/44 with origin AS214961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214961 in the RIR database for the space.634 of 636

Route objects not announced

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

2a10:4646:700::/44RIPEValid

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.