Network · data from 2026-11-12
AS13965 SBCIS-FYTVAR - AT&T Enterprises, LLC
Registry name: SBCIS-FYTVAR - AT&T Enterprises, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13965, 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.
| 107.121.190.0/23 | Invalid: origin | None | 2 0%low visibility |
| 107.121.192.0/21 | Invalid: origin | None | 2 0%low visibility |
| 2600:381:3900::/40 | No ROA | Other IRR onlyALTDB | 636 100% |
| 2600:387:14::/48 | No ROA | Other IRR onlyALTDB | 636 100% |
| 107.121.192.0/24 | Valid | Nonecovered by 107.121.192.0/23 | 673 100% |
| 107.121.193.0/24 | Valid | Nonecovered by 107.121.192.0/23 | 673 100% |
| 107.121.196.0/24 | Valid | Nonecovered by 107.121.196.0/23 | 673 100% |
| 107.121.197.0/24 | Valid | Nonecovered by 107.121.196.0/23 | 673 100% |
| 107.121.191.0/24 | Valid | RIR databaseARIN | 673 100% |
| 107.121.194.0/24 | Valid | RIR databaseARIN | 673 100% |
| 107.121.198.0/24 | Valid | RIR databaseARIN | 673 100% |
| 107.116.31.0/24 | Valid | RIR databaseALTDB, ARIN | 671 100% |
| 107.116.32.0/21 | Valid | RIR databaseALTDB, ARIN | 671 100% |
AS-SET
AS13965 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 15 are in fix.csv.
- ROA: origin2
- ROA: none2
- Route object: none6
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 107.121.190.0/23 | ROAs covering it name AS7018, not AS13965. If AS13965 should announce it, add a ROA for AS13965. |
| Route object: none | 107.121.190.0/23 | No route object for it. Add a route object with origin AS13965 in the RIR database for the space. |
| ROA: origin | 107.121.192.0/21 | ROAs covering it name AS7018, not AS13965. If AS13965 should announce it, add a ROA for AS13965. |
| Route object: none | 107.121.192.0/21 | No route object for it. Add a route object with origin AS13965 in the RIR database for the space. |
| ROA: none | 2600:381:3900::/40 | No ROA covers it. Add a ROA for AS13965, maxLength 40. |
| Route object: RIR | 2600:381:3900::/40 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2600:387:14::/48 | No ROA covers it. Add a ROA for AS13965, maxLength 48. |
| Route object: RIR | 2600:387:14::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 107.121.192.0/24 | No route object for it. A route object for 107.121.192.0/23 with origin AS13965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13965 in the RIR database for the space. |
| Route object: none | 107.121.193.0/24 | No route object for it. A route object for 107.121.192.0/23 with origin AS13965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13965 in the RIR database for the space. |
| Route object: none | 107.121.196.0/24 | No route object for it. A route object for 107.121.196.0/23 with origin AS13965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13965 in the RIR database for the space. |
| Route object: none | 107.121.197.0/24 | No route object for it. A route object for 107.121.196.0/23 with origin AS13965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13965 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13965 whose prefix no peer sees AS13965 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 107.121.192.0/23 | ARIN | Valid |
| 107.121.196.0/23 | ARIN | Valid |
| 2600:381:3880::/42 | ALTDB | 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.