Network · data from 2026-11-12
AS39961 CCSF
Registry name: CCSF - San Francisco Department of Telecommunications and Information Services, US · PeeringDB
13IPv4 routes
100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
13 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS39961, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS39961, 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.
| 208.121.5.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 673 100% |
| 208.121.32.0/20 | Valid | Nonecovered by 208.121.0.0/16 | 673 100% |
| 208.121.64.0/18 | Valid | Nonecovered by 208.121.0.0/16 | 673 100% |
| 208.121.128.0/17 | Valid | Nonecovered by 208.121.0.0/16 | 673 100% |
| 208.121.203.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 673 100% |
| 208.121.0.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.1.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.6.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.48.0/20 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.224.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.225.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.226.0/23 | Valid | Nonecovered by 208.121.0.0/16 | 672 100% |
| 208.121.230.0/24 | Valid | Nonecovered by 208.121.0.0/16 | 670 100% |
AS-SET
AS39961'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 15 are in fix.csv.
- Route object: none13
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 208.121.5.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.32.0/20 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.64.0/18 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.128.0/17 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.203.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.0.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.1.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.6.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.48.0/20 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.224.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.225.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.226.0/23 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
| Route object: none | 208.121.230.0/24 | No route object for it. A route object for 208.121.0.0/16 with origin AS39961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39961 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39961 whose prefix no peer sees AS39961 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 208.121.0.0/16 | ARIN | Valid |
| 2001:470:620::/48 | ARIN | Valid |
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.