Autonomous system
AS205013 JESSYU SHIH-CHIEH YU
Unclassified RIPE
Summary
JESSYU
individual ipv6 taiwan
JESSYU is held by JESSYU SHIH-CHIEH YU.
What it's used for
- The space carries a single IPv6 prefix,
2a0c:b641:7b0::/48, with no IPv4 addresses announced. - The inventory consists of 1 IPv6 prefix against 1 observed neighbour, indicating a minimal footprint typical of a personal or small-scale network.
- The operator is an individual, suggesting the traffic consists of personal endpoints or small-scale services rather than commercial subscriber traffic.
Notable
- The registry holder is listed as JESSYU SHIH-CHIEH YU, which aligns with the AS handle
JESSYU. - The address inventory is extremely small, comprising only one IPv6 /48 block, which does not fit the profile of a commercial ISP or large enterprise.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-08, 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 |
|---|---|---|
| TW | Taiwan, Province of China | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS205013- Registry name
- JESSYU
- Registrant
- jessyu4j-MNT
- Abuse contact
- contact@jessyu.tw
- Registered
- 2025-08-29
- Last changed
- 2025-09-25
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- JESSYU
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
RIPE::AS205013:AS-JESSYU- Website
- https://jws.jessyu.tw
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 AS205013
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 3 naming AS205013
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: 455 networks and 1,854 prefixes, as published 2026-11-09. 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