Network · data from 2026-11-12
AS7511 SYNAPSE
Registry name: SYNAPSE - SYNAPSE Co.,Ltd., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7511, 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.
| 101.53.104.0/21 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 110.92.32.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 124.146.64.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 124.146.96.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.95.32.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.208.160.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 203.111.192.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 203.140.160.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 203.145.96.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 203.147.112.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 210.146.80.0/20 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 210.237.32.0/19 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 101.50.60.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 103.53.120.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 103.208.96.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 202.79.0.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 202.79.8.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 202.79.12.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 219.100.8.0/22 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 2401:c800::/32 | Valid | Other IRR onlyJPIRR, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS7511: AS7511:AS-SYNAPSE AS7511:AS-SYNAPSE-IPV6. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS7511 isn't in the set, or no route object for AS7511 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS7511 in it | Not covered |
|---|---|---|---|---|---|
| AS7511:AS-SYNAPSE | RADB | 1 | 1 | Yes | 0 |
| JPIRR (also) | 1 | 1 | Yes | 0 | |
| AS7511:AS-SYNAPSE-IPV6 | RADB | 1 | 1 | Yes | 0 |
| JPIRR (also) | 1 | 1 | Yes | 0 |
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 20 are in fix.csv.
- Route object: RIR20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 101.53.104.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 110.92.32.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.146.64.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.146.96.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.95.32.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.208.160.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.111.192.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.140.160.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.145.96.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.147.112.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.146.80.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.237.32.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.50.60.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.53.120.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.208.96.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.79.0.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.79.8.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.79.12.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.8.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:c800::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS7511 is announced.
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.