Autonomous system
AS17626 YNL-AS-AP Yasuda Network LTD
Unclassified APNIC
Summary
Yasuda Network
business ipv6 small
YNL-AS-AP is the handle for Yasuda Network LTD.
What it's used for
- The address space is IPv6-only, carrying the single prefix
2001:df0:c940::/48. - With 0 IPv4 prefixes and 1 IPv6 prefix against 1 observed neighbour, the inventory suggests a small, self-contained network or a specific service deployment rather than a transit provider.
Notable
- The RDAP registrant lookup was unavailable, so registrant alignment with the announcer cannot be verified from this pack.
- The address inventory consists of a single /48 block, indicating a minimal footprint.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS45691 | DODO K.K. | 37 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-24, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 0 prefixes · 0 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 1 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS17626- Registry name
- YNL-AS-AP
- Registrant
- Yasuda Network LTD
- Abuse contact
- abuse@yasudanet.com
- Registered
- 2024-06-24
- Last changed
- 2024-06-25
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Yasuda Network
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Present at
- 1 exchanges
- Website
- http://yasudanet.com
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS17626
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS17626
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 443 networks and 1,779 prefixes, as published 2026-10-25. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere