AS63776
MERCARI
Japan (JP)
ASN Information
| AS Number | AS63776 |
|---|---|
| AS Name | MERCARI-JP |
| Organization | Mercari, Inc. |
| Also known as | MERCARI |
| Country | Japan (JP) |
| Registry | APNIC |
| ASN Type | Content |
| Last Seen | Not available |
| Announcement Count | Source unavailable |
| IPv4 Prefix Count | Source unavailable |
| IPv6 Prefix Count | Source unavailable |
| RPKI Status | Source unavailable |
| IRR Records | Available (5 route objects) |
| PeeringDB | View on PeeringDB ↗ |
| Website | https://www.mercari.com/jp/ ↗ |
AS Path to AS63776
No AS paths were returned for this AS.
Route Collectors (Visibility)
No RouteViews collector currently carries this AS's routes.
Announced Prefixes (0)
View All →Source unavailable: the prefix list could not be retrieved from RouteViews.
Peers (3)
View All →| AS | Name | Relationship | Paths | Last Seen |
|---|---|---|---|---|
| AS2914 | NTT-DATA-2914 - NTT America, Inc. | Upstream (inferred) | RIPEstat only | — |
| AS17676 | GIGAINFRA - SoftBank Corp. | Upstream (inferred) | RIPEstat only | — |
| AS17686 | ACCELIA - ACCELIA | Upstream (inferred) | RIPEstat only | — |
Neighbours seen next to AS63776 in public AS paths. These are not confirmed BGP sessions; peer IP addresses and locations are not published by these sources.
IX Presence (1)
IX Updates →| Exchange | Location | IPv4 | IPv6 | Speed | RS peer | Updated |
|---|---|---|---|---|---|---|
| BBIX Tokyo | Tokyo, JP | 101.203.89.41 | 2001:de8:c::6:3776:1 | 10G | Yes |
IX ports AS63776 has registered in PeeringDB (self-reported).
Upstreams (3)
Downstreams (0)
No downstream ASNs found for AS63776 in current data sources.
Registry and PeeringDB details
| Holder (RIPEstat) | MERCARI-JP - Mercari, Inc. |
|---|---|
| Registered | Yes |
| Peering policy | Selective |
| IRR AS-set | JPIRR::AS-MERCARI |
| Registry record last modified | |
| Maintainers | Not available |
| Internet exchanges (PeeringDB) | 1 |
| Facilities (PeeringDB) | 1 |
| PeeringDB record updated |
Data sources for this page
3 sources could not be reached. Sections that depend on them may be incomplete; missing data does not mean there are no records.
| Source | Freshness | Result | Fetched | Provider observation | Error |
|---|---|---|---|---|---|
| RouteViews API | Unavailable | Source unavailable | Never | Not reported | RouteViews API: outbound queue full (would wait 13s) |
| RIPEstat Data API | Live | OK | Not reported | None | |
| PeeringDB | Live | OK | Not reported | None | |
| RouteViews API | Unavailable | Source unavailable | Never | Not reported | RouteViews API: outbound queue full (would wait 13s) |
| RouteViews API | Unavailable | Source unavailable | Never | Not reported | RouteViews API: outbound queue full (would wait 13s) |
| RIPEstat Data API (AS names) | Cached | OK | Not reported | None | |
| NLNOG IRRexplorer | Live | OK | Not reported | None | |
| PeeringDB (exchanges) | Cached | OK | Not reported | None |
Page generated . See data sources and limitations.