AS 152565
Our autonomous system: where we are, what we announce, how to peer, and how to report abuse.
At a glance
- ASN
- AS152565 — JOYSVC-AS-IN — JOY SERVICES
- Registry
- APNIC (allocated), maintained by MAINT-IN-JOYSVC and MAINT-IN-IRINN; IRT-JOYSVC-IN
- Country
- India (IN)
- Network type
- Content · server hosting · direct feed
- Peers
- 394 (#4 in India)
- Upstreams
- 5 — Sify, Web Werks, Sucura Networks, BiMajLink, CtrlS
- Downstreams
- 18 networks (customer cone 31)
- IPv4
- 13 prefixes, 31 × /24
- IPv6
- 6 prefixes, 32,773 × /48
- Peering
- peering@joy.services · open policy
- NOC
- noc@joy.services · 24/7
- Abuse
- abuse@joy.services
- Locations
- Noida, Mumbai, Chennai, Singapore, USA
What we announce
AS152565 originates its own address space and, under BYOIP agreements, prefixes belonging to customers who route through us. All announcements carry RPKI ROAs; we drop RPKI-invalid routes from peers and upstreams. The full prefix lists with holders are on the infrastructure page. IPv4 blocks include 138.252.100.0/24, 138.252.101.0/24, 157.20.240.0/23, 161.248.162.0/24, 161.248.163.0/24, 46.232.234.0/24 and 201.7.16.0/24 (Joy Services / Joy Data Services); IPv6 includes 2401:e920::/33 and 2001:df4:940::/48.
Where we are
Compute regions in Noida (Delhi NCR), Mumbai, Chennai, Singapore and the US West Coast, connected by a 500+ Gbps backbone. We peer at the major Indian exchanges in Mumbai and Delhi, in Singapore and on the US West Coast, and buy transit from five upstreams for global reach. The Mumbai region is the flagship — 100 Gbps uplinks and the primary DDoS scrubbing centre.
How to peer
- Email peering@joy.services with your ASN, the exchange(s) or facility, expected traffic and whether you want IPv4, IPv6 or both.
- We check your IRR / RPKI data and reply with session parameters; for more than 1 Gbps we prefer bilateral sessions, otherwise the route servers are fine.
- Both sides configure; we verify prefixes and confirm turn-up. We usually complete this within a few business days.
We expect peers to keep IRR objects and ROAs current, to announce only their own and their customers' prefixes, and not to point default at us. Details and pricing for transit, IX ports and Virtual Connect are on the peering page.
Reporting abuse
If you see attacks, spam, scanning or copyright infringement from a Joy address, email abuse@joy.services with the source IP, destination, timestamps in UTC and log excerpts. Reports are acknowledged automatically and reviewed by a human within one business day; confirmed violations lead to suspension under the Acceptable Use Policy. Please do not send abuse reports to peering@ or noc@ — they are routed to different teams.
Looking glass and data
A public looking glass with ping, traceroute and BGP route lookups from each region is available on request to peers and customers. Public route data for AS152565 is available at the usual BGP data sources; the numbers on this page are refreshed from them. The status page shows backbone and scrubbing health in real time and publishes incidents affecting routing.
Security and routing hygiene
- RPKI ROAs for every originated prefix; RPKI-invalid routes dropped at all borders.
- Prefix filters generated from IRR AS-SETs for customers and peers, refreshed nightly.
- Maximum-prefix limits on every session; BGP sessions authenticated with MD5 or TCP-AO where supported.
- uRPF on customer ports; spoofed traffic does not leave AS152565.
- Blackhole community 152565:666 honoured from customers; traffic-engineering communities documented on the peering page.
- NeuroMesh NetFlow telemetry is encrypted end to end; flow records are kept 30 days for security analysis.