Network · data from 2026-11-12
AS134534 ATT-NBE-SG - ATT NBE Equinix Singapore
Registry name: ATT-NBE-SG - ATT NBE Equinix Singapore, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134534, 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.
| 27.111.227.176/28 | Invalid: origin | None | 1 0%low visibility |
| 27.111.227.224/28 | Invalid: origin | None | 1 0%low visibility |
| 202.79.209.208/28 | Invalid: origin | None | 1 0%low visibility |
| 202.79.215.64/26 | Invalid: origin | None | 1 0%low visibility |
| 203.163.94.0/24 | No ROA | Other origin only | 172 26% |
| 32.24.88.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 210.7.102.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.7.103.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS134534 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 17 are in fix.csv.
- ROA: origin4
- ROA: none4
- Route object: none5
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 27.111.227.176/28 | ROAs covering it name AS15830, not AS134534. If AS134534 should announce it, add a ROA for AS134534. |
| Route object: none | 27.111.227.176/28 | No route object for it. Add a route object with origin AS134534 in the RIR database for the space. |
| ROA: origin | 27.111.227.224/28 | ROAs covering it name AS15830, not AS134534. If AS134534 should announce it, add a ROA for AS134534. |
| Route object: none | 27.111.227.224/28 | No route object for it. Add a route object with origin AS134534 in the RIR database for the space. |
| ROA: origin | 202.79.209.208/28 | ROAs covering it name AS15830, not AS134534. If AS134534 should announce it, add a ROA for AS134534. |
| Route object: none | 202.79.209.208/28 | No route object for it. Add a route object with origin AS134534 in the RIR database for the space. |
| ROA: origin | 202.79.215.64/26 | ROAs covering it name AS15830, not AS134534. If AS134534 should announce it, add a ROA for AS134534. |
| Route object: none | 202.79.215.64/26 | No route object for it. Add a route object with origin AS134534 in the RIR database for the space. |
| ROA: none | 203.163.94.0/24 | No ROA covers it. Add a ROA for AS134534, maxLength 24. |
| Route object: none | 203.163.94.0/24 | Route objects for it name AS2687. Add a route object with origin AS134534 in the RIR database for the space. |
| ROA: none | 32.24.88.0/24 | No ROA covers it. Add a ROA for AS134534, maxLength 24. |
| Route object: RIR | 32.24.88.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 210.7.102.0/24 | No ROA covers it. Add a ROA for AS134534, maxLength 24. |
| Route object: RIR | 210.7.102.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.7.103.0/24 | No ROA covers it. Add a ROA for AS134534, maxLength 24. |
| Route object: RIR | 210.7.103.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS134534 whose prefix no peer sees AS134534 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 122.248.129.0/24 | NTTCOM, RADB | 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.