Network · data from 2026-11-12
AS11574 SFGNET-AS - San Francisco Baseball Associates LLC
Registry name: SFGNET-AS - San Francisco Baseball Associates LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11574, 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.
| 130.12.191.0/24 | No ROA | None | 667 99% |
AS-SET
AS11574 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 7 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 130.12.191.0/24 | No ROA covers it. Add a ROA for AS11574, maxLength 24. |
| Route object: none | 130.12.191.0/24 | No route object for it. Add a route object with origin AS11574 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11574 whose prefix no peer sees AS11574 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.64.148.0/22 | NTTCOM | No ROA |
| 63.93.132.0/22 | NTTCOM | No ROA |
| 151.181.229.0/24 | RADB | No ROA |
| 208.232.58.0/23 | NTTCOM | No ROA |
| 208.240.251.0/24 | NTTCOM | No ROA |
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.