Routing security
AS7663 FFNET FUJIMIC INC.
Hosting ARIN Content
Announcements
What this network originates
Every prefix observed with AS7663 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 210.167.32.0/24 | No ROA | IRR | 52 |
| 210.167.34.0/24 | No ROA | IRR | 52 |
| 210.167.35.0/24 | No ROA | IRR | 52 |
| 210.167.40.0/24 | No ROA | IRR | 52 |
| 210.167.41.0/24 | No ROA | IRR | 52 |
| 210.167.42.0/24 | No ROA | IRR | 52 |
| 210.167.43.0/24 | No ROA | IRR | 52 |
| 210.167.51.0/24 | No ROA | IRR | 52 |
| 210.167.52.0/24 | No ROA | IRR | 52 |
| 210.167.62.0/24 | No ROA | IRR | 52 |
| 210.167.63.0/24 | No ROA | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS7663 may originate these prefixes, up to the maximum length shown.
No ROA names this AS as an authorised origin.
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS7663 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 210.167.32.0/19 | RADB | FFNET CIDR BLOCK 1 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.33.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.33.0/24 | RADB | FFNET CIDR BLOCK 02 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.36.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.36.0/24 | RADB | FFNET CIDR BLOCK 05 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.37.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.37.0/24 | RADB | FFNET CIDR BLOCK 06 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.38.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.38.0/24 | RADB | FFNET CIDR BLOCK 07 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.39.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.39.0/24 | RADB | FFNET CIDR BLOCK 08 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.44.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.44.0/24 | RADB | FFNET CIDR BLOCK 13 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.45.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.45.0/24 | RADB | FFNET CIDR BLOCK 14 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.46.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.46.0/24 | RADB | FFNET CIDR BLOCK 15 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.47.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.47.0/24 | RADB | FFNET CIDR BLOCK 16 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.48.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.48.0/24 | RADB | FFNET CIDR BLOCK 17 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.49.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.49.0/24 | RADB | FFNET CIDR BLOCK 18 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.50.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.50.0/24 | RADB | FFNET CIDR BLOCK 19 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.53.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.53.0/24 | RADB | FFNET CIDR BLOCK 22 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.54.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.54.0/24 | RADB | FFNET CIDR BLOCK 23 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.55.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.55.0/24 | RADB | FFNET CIDR BLOCK 24 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.56.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.56.0/24 | RADB | FFNET CIDR BLOCK 25 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.57.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.57.0/24 | RADB | FFNET CIDR BLOCK 26 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.58.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.58.0/24 | RADB | FFNET CIDR BLOCK 27 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.59.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.59.0/24 | RADB | FFNET CIDR BLOCK 28 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.60.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.60.0/24 | RADB | FFNET CIDR BLOCK 29 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.61.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Not announced |
| 210.167.61.0/24 | RADB | FFNET CIDR BLOCK 30 | MAINT-AS7663 | 2023-11-13 | Not announced |
| 210.167.32.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.32.0/24 | RADB | FFNET CIDR BLOCK 01 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.34.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.34.0/24 | RADB | FFNET CIDR BLOCK 03 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.35.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.35.0/24 | RADB | FFNET CIDR BLOCK 04 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.40.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.40.0/24 | RADB | FFNET CIDR BLOCK 09 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.41.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.41.0/24 | RADB | FFNET CIDR BLOCK 10 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.42.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.42.0/24 | RADB | FFNET CIDR BLOCK 11 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.43.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.43.0/24 | RADB | FFNET CIDR BLOCK 12 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.51.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.51.0/24 | RADB | FFNET CIDR BLOCK 20 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.52.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.52.0/24 | RADB | FFNET CIDR BLOCK 21 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.62.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.62.0/24 | RADB | FFNET CIDR BLOCK 31 | MAINT-AS7663 | 2023-11-13 | Announced |
| 210.167.63.0/24 | NTTCOM | FUJIMIC, Inc.-161257 | MAINT-EQUINIXPAC | 2022-06-08 | Announced |
| 210.167.63.0/24 | RADB | FFNET CIDR BLOCK 32 | MAINT-AS7663 | 2023-11-13 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS7663 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-EQUINIX-TY | RADB | Lists AS7663 as a direct member |
AS-IIJ | RADB | Lists AS7663 as a direct member |
AS-KDD | RADB | Lists AS7663 as a direct member |
AS-KDDDMPEER | RADB | Lists AS7663 as a direct member |
AS-TELSTRA-INTL-CUSTOMERS | RADB | Lists AS7663 as a direct member |
AS2497:AS-IIJ | RADB | Lists AS7663 as a direct member |
RPKI from rpki-client, validated 2026-10-30 12:03 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-30. Cross-check on bgp.he.net.