bgpreport

Network · data from 2026-11-12

AS202023 Only

Registry name: OSP-AS Scaleway SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202023, 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.

139.26.0.0/21 Valid Nonecovered by 139.26.0.0/17 670 100% 68
139.26.8.0/21 Valid Nonecovered by 139.26.0.0/17 670 100% 68
139.26.16.0/21 Valid Nonecovered by 139.26.0.0/17 670 100% 68
139.26.24.0/21 Valid Nonecovered by 139.26.0.0/17 670 100% 68
2c0f:3781:2220::/44 Valid Nonecovered by 2c0f:3781::/32 633 100% 67
2c0f:3781:2250::/44 Valid Nonecovered by 2c0f:3781::/32 633 100% 67
2c0f:3781:2100::/44 Valid Nonecovered by 2c0f:3781::/32 632 99% 67
2c0f:3781:2210::/44 Valid Nonecovered by 2c0f:3781::/32 632 99% 67
2c0f:3781:2230::/44 Valid Nonecovered by 2c0f:3781::/32 632 99% 67
2c0f:3781:2240::/44 Valid Nonecovered by 2c0f:3781::/32 632 99% 67
139.26.0.0/17 Valid RIR databaseAFRINIC 670 100% 68
2c0f:3781::/32 Valid RIR databaseAFRINIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS202023: AS-TELCOOI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS202023 isn't in the set, or no route object for AS202023 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS202023 in itNot covered
AS-TELCOOI AFRINIC 218 Yes 0

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

  • Route object: none10
ChangePrefix or setDetailFull-table peers
Route object: none139.26.0.0/21No route object for it. A route object for 139.26.0.0/17 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.670 of 673
Route object: none139.26.8.0/21No route object for it. A route object for 139.26.0.0/17 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.670 of 673
Route object: none139.26.16.0/21No route object for it. A route object for 139.26.0.0/17 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.670 of 673
Route object: none139.26.24.0/21No route object for it. A route object for 139.26.0.0/17 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.670 of 673
Route object: none2c0f:3781:2220::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.633 of 636
Route object: none2c0f:3781:2250::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.633 of 636
Route object: none2c0f:3781:2100::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.632 of 636
Route object: none2c0f:3781:2210::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.632 of 636
Route object: none2c0f:3781:2230::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.632 of 636
Route object: none2c0f:3781:2240::/44No route object for it. A route object for 2c0f:3781::/32 with origin AS202023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202023 in the RIR database for the space.632 of 636

Route objects not announced

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