Registration
IPv4 Prefixes
18 prefixes · 3,328 addresses · 8 top-level Routing data as of 2026-10-05 16:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 38.253.237.0/24 | 38.253.237.0 – 38.253.237.255 | 256 |
| 38.253.250.0/23 | 38.253.250.0 – 38.253.251.255 | 512 |
| 38.253.250.0/24 | 38.253.250.0 – 38.253.250.255 | 256 |
| 38.253.251.0/24 | 38.253.251.0 – 38.253.251.255 | 256 |
| 103.148.188.0/24 | 103.148.188.0 – 103.148.188.255 | 256 |
| 103.148.189.0/24 | 103.148.189.0 – 103.148.189.255 | 256 |
| 103.208.204.0/22 | 103.208.204.0 – 103.208.207.255 | 1,024 |
| 103.208.204.0/23 | 103.208.204.0 – 103.208.205.255 | 512 |
| 103.208.204.0/24 | 103.208.204.0 – 103.208.204.255 | 256 |
| 103.208.205.0/24 | 103.208.205.0 – 103.208.205.255 | 256 |
| 103.208.206.0/23 | 103.208.206.0 – 103.208.207.255 | 512 |
| 103.208.206.0/24 | 103.208.206.0 – 103.208.206.255 | 256 |
| 103.208.207.0/24 | 103.208.207.0 – 103.208.207.255 | 256 |
| 113.192.26.0/24 | 113.192.26.0 – 113.192.26.255 | 256 |
| 113.192.27.0/24 | 113.192.27.0 – 113.192.27.255 | 256 |
| 113.192.28.0/23 | 113.192.28.0 – 113.192.29.255 | 512 |
| 113.192.28.0/24 | 113.192.28.0 – 113.192.28.255 | 256 |
| 113.192.29.0/24 | 113.192.29.0 – 113.192.29.255 | 256 |
IPv6 Prefixes
1 prefix · 1 × /48 Routing data as of 2026-10-05 16:00 UTC
| Prefix | Addresses |
|---|---|
| 2404:4780:: | 280 |
BGP Neighbours
4 unique neighbours · 2 upstream/peer · 0 downstream · 2 collector-only. A neighbour can be seen on more than one side. Rows are ordered by AS paths: the number of BGP paths seen by RIPE RIS that contain the adjacency. Sightings count each IPv4/IPv6 route with the adjacency once per RIS peer that sees it (routes × peers), so they show how widely it is seen, not how many distinct routes it carries. Networks seen to the left of this AS in BGP paths, toward the route collectors — typically its transit providers (upstreams) and peers. Networks seen to the left of this AS only when they peer directly with a RIPE RIS route collector, so the adjacency may be an artefact of that peering; many of them also appear on the downstream side. Upstream & peer side (2)
Collector-only (2)
Raw RDAP Response
{
"rdapConformance": [
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"notices": [
{
"title": "Source",
"description": [
"Objects returned came from source",
"IDNIC"
]
},
{
"title": "Terms and Conditions",
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format.",
"This information has been partially mirrored by APNIC from IDNIC."
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/134651",
"rel": "terms-of-service",
"href": "http://www.apnic.net/db/dbcopyright.html",
"type": "text/html"
}
]
},
{
"title": "Whois Inaccuracy Reporting",
"description": [
"If you see inaccuracies in the results, please visit: "
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/134651",
"rel": "inaccuracy-report",
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"type": "text/html"
}
]
}
],
"country": "ID",
"name": "YETOYA-AS-ID",
"status": [
"active"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:30:34Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-02-10T03:14:53Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/134651",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/autnum/134651",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"PT Yetoya Solusi Indonesia",
"Internet Service Provider",
"Jakarta"
],
"title": "description"
},
{
"description": [
"Send Spam & Abuse reports to: [email protected]"
],
"title": "remarks"
}
],
"entities": [
{
"roles": [
"administrative",
"technical"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:26:01Z"
},
{
"eventAction": "last changed",
"eventDate": "2023-08-28T07:57:45Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/134651",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/entity/HU38-AP",
"type": "application/rdap+json"
}
],
"handle": "HU38-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
},
{
"roles": [
"abuse"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:26:01Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-01-29T08:15:41Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/134651",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/entity/IRT-YETOYA-ID",
"type": "application/rdap+json"
}
],
"handle": "IRT-YETOYA-ID",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-YETOYA-ID"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "PT. Yetoya Solusi Indonesia\nJl. Tanah Merdeka No. 1, Rt.010 / Rw.003\nKel.Rambutan, Kec. Ciracas\nJakarta Timur"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
}
],
"handle": "AS134651",
"startAutnum": 134651,
"endAutnum": 134651,
"objectClassName": "autnum",
"port43": "whois.apnic.net"
} Contact details of private individuals are redacted.