Registration
IPv4 Prefixes
21 prefixes · 5,376 addresses Routing data as of 2026-10-11 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 43.243.212.0/24 | 43.243.212.0 – 43.243.212.255 | 256 |
| 43.243.213.0/24 | 43.243.213.0 – 43.243.213.255 | 256 |
| 43.243.214.0/24 | 43.243.214.0 – 43.243.214.255 | 256 |
| 43.243.215.0/24 | 43.243.215.0 – 43.243.215.255 | 256 |
| 43.252.32.0/24 | 43.252.32.0 – 43.252.32.255 | 256 |
| 43.252.34.0/24 | 43.252.34.0 – 43.252.34.255 | 256 |
| 43.252.35.0/24 | 43.252.35.0 – 43.252.35.255 | 256 |
| 103.69.112.0/24 | 103.69.112.0 – 103.69.112.255 | 256 |
| 103.69.113.0/24 | 103.69.113.0 – 103.69.113.255 | 256 |
| 103.69.114.0/24 | 103.69.114.0 – 103.69.114.255 | 256 |
| 103.69.115.0/24 | 103.69.115.0 – 103.69.115.255 | 256 |
| 103.129.206.0/24 | 103.129.206.0 – 103.129.206.255 | 256 |
| 103.166.119.0/24 | 103.166.119.0 – 103.166.119.255 | 256 |
| 103.252.4.0/24 | 103.252.4.0 – 103.252.4.255 | 256 |
| 103.252.5.0/24 | 103.252.5.0 – 103.252.5.255 | 256 |
| 103.252.6.0/24 | 103.252.6.0 – 103.252.6.255 | 256 |
| 103.252.7.0/24 | 103.252.7.0 – 103.252.7.255 | 256 |
| 103.253.200.0/24 | 103.253.200.0 – 103.253.200.255 | 256 |
| 103.253.201.0/24 | 103.253.201.0 – 103.253.201.255 | 256 |
| 103.253.202.0/24 | 103.253.202.0 – 103.253.202.255 | 256 |
| 103.253.203.0/24 | 103.253.203.0 – 103.253.203.255 | 256 |
IPv6 Prefixes
16 prefixes · 16 × /48 Routing data as of 2026-10-11 00:00 UTC
| Prefix | Addresses |
|---|---|
| 2402:540:1:: | 280 |
| 2402:540:2:: | 280 |
| 2402:540:3:: | 280 |
| 2402:540:4:: | 280 |
| 2402:540:5:: | 280 |
| 2402:540:6:: | 280 |
| 2402:540:7:: | 280 |
| 2402:540:8:: | 280 |
| 2402:540:9:: | 280 |
| 2402:540:a:: | 280 |
| 2402:540:b:: | 280 |
| 2402:540:c:: | 280 |
| 2402:540:d:: | 280 |
| 2402:540:e:: | 280 |
| 2402:540:f:: | 280 |
| 2402:540:10:: | 280 |
BGP Neighbours
12 unique neighbours · 4 upstream/peer · 4 downstream · 4 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 right of this AS in BGP paths — networks whose routes it carries, typically its customers (downstreams). 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 (4)
Downstream side (4)
Collector-only (4)
Raw RDAP Response
{
"rdapConformance": [
"history_version_0",
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"notices": [
{
"title": "Source",
"description": [
"Objects returned came from source",
"APNIC"
]
},
{
"title": "Terms and Conditions",
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format."
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/132996",
"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://rdap.apnic.net/autnum/132996",
"rel": "inaccuracy-report",
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"type": "text/html"
}
]
}
],
"country": "IN",
"name": "ThreesaInfoway-AS",
"status": [
"active"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2013-10-28T11:44:16Z"
},
{
"eventAction": "last changed",
"eventDate": "2018-12-13T07:11:55Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/132996",
"rel": "self",
"href": "https://rdap.apnic.net/autnum/132996",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"Threesa Infoway Pvt.Ltd."
],
"title": "description"
},
{
"description": [
"send spam and abuse report to [email protected]"
],
"title": "remarks"
}
],
"entities": [
{
"roles": [
"technical",
"administrative"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2017-11-17T07:32:00Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-09-27T09:52:19Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/132996",
"rel": "self",
"href": "https://rdap.apnic.net/entity/YB656-AP",
"type": "application/rdap+json"
}
],
"handle": "YB656-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
},
{
"roles": [
"abuse"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2017-11-17T07:35:34Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-09-26T06:25:31Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/132996",
"rel": "self",
"href": "https://rdap.apnic.net/entity/IRT-THREESAINFOWAY-IN",
"type": "application/rdap+json"
}
],
"handle": "IRT-THREESAINFOWAY-IN",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-THREESAINFOWAY-IN"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "Shop No.4, First floor,Anand Ram Laghu Sankul vasant vihar Thane w,Navi Mumbai,Maharashtra-400610"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
}
],
"handle": "AS132996",
"startAutnum": 132996,
"endAutnum": 132996,
"objectClassName": "autnum",
"port43": "whois.apnic.net"
} Contact details of private individuals are redacted.