bgpreport

Network · data from 2026-11-12

AS202623 CLOUDFLARENET-CORE Cloudflare Inc

Registry name: CLOUDFLARENET-CORE Cloudflare Inc, US · not in PeeringDB

12IPv4 routes 91.7% RPKI valid · 33.3% with a route object
24IPv6 routes 100.0% RPKI valid · 29.2% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 25 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS202623, seen from no peer

Announced routes

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

172.71.64.0/20 No ROA None 673 100% 67
104.23.32.0/19 Valid None 673 100% 67
104.23.64.0/19 Valid None 673 100% 67
141.101.64.0/24 Valid Other origin only 673 100% 67
141.101.91.0/24 Valid None 673 100% 67
172.71.32.0/19 Valid None 673 100% 67
198.41.143.0/24 Valid Other origin only 673 100% 67
198.41.253.0/24 Valid Other origin only 673 100% 67
2a06:98c0:3626::/48 Valid None 636 100% 67
2a06:98c0:3627::/48 Valid None 636 100% 67
2a06:98c0:362b::/48 Valid None 636 100% 67
2a06:98c0:362c::/48 Valid None 636 100% 67
2a06:98c0:362d::/48 Valid None 636 100% 67
2a06:98c0:3630::/48 Valid None 636 100% 67
2a06:98c0:3631::/48 Valid None 636 100% 67
2a06:98c0:3632::/48 Valid None 636 100% 67
2a06:98c0:3635::/48 Valid None 636 100% 67
2a06:98c0:3636::/48 Valid None 636 100% 67
2a06:98c0:360e::/48 Valid None 635 100% 67
2a06:98c0:3612::/48 Valid None 635 100% 67
2a06:98c0:3616::/48 Valid None 635 100% 67
2a06:98c0:362f::/48 Valid None 635 100% 67
2a06:98c0:3634::/48 Valid None 635 100% 67
2a06:98c0:3637::/48 Valid None 635 100% 67
2a06:98c0:3622::/48 Valid None 1 0%low visibility 1
162.159.83.0/24 Valid RIR databaseARIN 673 100% 67
198.41.150.0/24 Valid RIR databaseARIN 673 100% 67
198.41.252.0/24 Valid RIR databaseARIN 673 100% 67
2400:cb00:1028::/48 Valid RIR databaseAPNIC 636 100% 67
2400:cb00:1029::/48 Valid RIR databaseAPNIC 636 100% 67
2400:cb00:420::/48 Valid RIR databaseAPNIC 635 100% 67
2a06:98c0:1401::/48 Valid RIR databaseRIPE 635 100% 67
198.41.245.0/24 Valid RIR databaseARIN 253 38% 44
2a06:98c0:3605::/48 Valid RIR databaseRIPE 189 30% 40
2a06:98c0:3607::/48 Valid RIR databaseRIPE 189 30% 40
2a06:98c0:3606::/48 Valid RIR databaseRIPE 185 29% 40

AS-SET

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

  • ROA: none1
  • Route object: none25
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none172.71.64.0/20No ROA covers it. Add a ROA for AS202623, maxLength 20.673 of 673
Route object: none172.71.64.0/20No route object for it. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none104.23.32.0/19No route object for it. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none104.23.64.0/19No route object for it. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none141.101.64.0/24Route objects for it name AS13335. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none141.101.91.0/24No route object for it. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none172.71.32.0/19No route object for it. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none198.41.143.0/24Route objects for it name AS13335. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none198.41.253.0/24Route objects for it name AS13335. Add a route object with origin AS202623 in the RIR database for the space.673 of 673
Route object: none2a06:98c0:3626::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3627::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:362b::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:362c::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:362d::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3630::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3631::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3632::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3635::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:3636::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.636 of 636
Route object: none2a06:98c0:360e::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:3612::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:3616::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:362f::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:3634::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:3637::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.635 of 636
Route object: none2a06:98c0:3622::/48No route object for it. Add a route object with origin AS202623 in the RIR database for the space.1 of 636

Route objects not announced

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

198.41.148.0/22ARINValid
198.41.148.0/24ARINValid
198.41.152.0/22ARINValid
198.41.244.0/23ARINNo ROA
198.41.244.0/24ARINValid
198.41.254.0/23ARINNo ROA
2a06:98c0:1400::/48RIPEValid
2a06:98c0:3602::/47RIPENo ROA
2a06:98c0:3603::/48RIPEValid
2a06:98c0:3604::/47RIPENo ROA
2a06:98c0:3604::/48RIPEValid

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.