Joy Services
All systems operational Sign in
JoyNetworkGlobal infrastructure

Five regions. One network we built.

Compute in Noida, Mumbai, Chennai, Singapore and US West, joined by fiber we own between our metros and by our own backbone on our own autonomous system, lit at exchanges on two continents and interconnected inside the data center and across the world. Every region shares the same DDoS filtering, the same templates and the same console. Two Joy data centers — Mumbai and Noida — are under construction next to the fiber.

AS152565 · own address space14 points of presence lit · 7 plannedOwn fiber: 2 routes1,816 hypervisor cores · 13,093 GB RAM
01 Regions
Where you can deploy

Choose by latency, not by brochure.

Pick the region nearest your users. Availability on the cards is live: a region accepts deploys when it has addresses, verified templates and a hypervisor answering.

ASIA-SOUTH / NOIDA

Noida, India

ACCEPTING DEPLOYS

Tier III facility in the NCR corridor; dual power feeds, N+1 cooling.

Uplink
100 Gbps · DDoS always-on
Delhi NCR
< 5 ms
Mumbai
~28 ms
Singapore
~80 ms
Templates
Ubuntu 22.04 LTS · Ubuntu 24.04 LTS · Windows Server 2022 · Windows Server 2025 · Windows Server 2019
ASIA-SOUTH / MUMBAI

Mumbai, India

ACCEPTING DEPLOYS

Flagship region — 100 Gbps uplinks, Mumbai IX peering and the primary scrubbing centre.

Uplink
100 Gbps · DDoS always-on
Mumbai
< 3 ms
Chennai
~22 ms
Singapore
~55 ms
Templates
Ubuntu 22.04 LTS · Ubuntu 24.04 LTS · Windows Server 2022 · Windows Server 2025 · Windows Server 2019
ASIA-SOUTH / CHENNAI

Chennai, India

LIMITED CAPACITY

Southern India coverage with submarine-cable proximity for Southeast Asian routes.

Uplink
10 Gbps · DDoS always-on
Chennai
< 4 ms
Bengaluru
~12 ms
Singapore
~40 ms
Templates
Ubuntu 22.04 LTS · Windows Server 2022
ASIA-SOUTHEAST / SG

Singapore

PROVISIONING

Regional hub for ASEAN traffic; direct paths to major Singapore exchanges.

Uplink
10 Gbps · DDoS always-on
Singapore
< 2 ms
Jakarta
~18 ms
Mumbai
~55 ms
Templates
Templates published at launch
NA-WEST / US

United States

LIMITED CAPACITY

West-coast presence for North American users and low-latency transpacific routes.

Uplink
10 Gbps · DDoS always-on
US West
< 10 ms
US East
~65 ms
Mumbai
~230 ms
Templates
Ubuntu 22.04 LTS · Windows Server 2022
02 The network we built
Fiber, backbone, interconnection

One autonomous system, edge to core.

Filled points are lit today; hollow ones are planned and listed as such. Green lines are fiber we own, blue our backbone and international capacity. Drag the globe; click a point to find it in the list. The list is content we keep by hand — the status page is the live one.

compute regionpoint of presence · exchangeedgeplannedfiber we ownbackboneinternational
REGIONDelhi NCRCompute region (Noida) · own fiber · interconnection · Joy DC Noida under construction · 6 links
REGIONMumbaiFlagship region · own fiber · scrubbing centre · exchange presence · Joy DC Mumbai under construction · 10 links
REGIONChennaiCompute region · own fiber · submarine-cable proximity · 4 links
POPPuneMetro point of presence · 1 link
POPIndorePoint of presence · exchange · 1 link
POPLucknowPoint of presence · 2 links
EDGENagpurEdge · 1 link
POPKolkataPoint of presence · eastern gateway · 4 links
POPBhubaneswarPoint of presence · 1 link
POPDhakaPoint of presence · exchange · 1 link
REGIONSingaporeCompute region · ASEAN hub · exchange presence · 5 links
POPLondonPoint of presence · exchange · 4 links
POPFrankfurtPoint of presence · exchange · 2 links
REGIONUS WestCompute region · transpacific landing · 2 links
PLANNEDDubaiPlanned edge · Gulf landing · 2 links
PLANNEDAmsterdamPlanned edge · 1 link
PLANNEDUS EastPlanned edge · 3 links
PLANNEDTokyoPlanned edge · 1 link
PLANNEDSydneyPlanned edge · 1 link
PLANNEDSão PauloPlanned edge · 1 link
PLANNEDJohannesburgPlanned edge · 1 link
03 Backbone
What we own and what we lit

Fiber, backbone, exchanges, and two buildings of our own.

LinkKindWhat it is
Delhi NCR — MumbaiFiber we ownFiber pairs we own between our own points of presence
Mumbai — ChennaiFiber we ownFiber pairs we own between our own points of presence
Delhi NCR — ChennaiBackboneBackbone between our metros, protected end to end
Mumbai — PuneMetroBackbone between our metros, protected end to end
Mumbai — IndoreBackboneBackbone between our metros, protected end to end
Mumbai — NagpurBackboneBackbone between our metros, protected end to end
Mumbai — LucknowBackboneBackbone between our metros, protected end to end
Delhi NCR — LucknowBackboneBackbone between our metros, protected end to end
Delhi NCR — KolkataBackboneBackbone between our metros, protected end to end
Kolkata — BhubaneswarBackboneBackbone between our metros, protected end to end
Kolkata — ChennaiBackboneBackbone between our metros, protected end to end
Kolkata — DhakaInternationalInternational capacity on our autonomous system
Mumbai — SingaporeInternationalInternational capacity on our autonomous system
Chennai — SingaporeInternationalInternational capacity on our autonomous system
Mumbai — LondonInternationalInternational capacity on our autonomous system
Mumbai — FrankfurtInternationalInternational capacity on our autonomous system
Delhi NCR — LondonInternationalInternational capacity on our autonomous system
Delhi NCR — FrankfurtInternationalInternational capacity on our autonomous system
Singapore — US WestInternationalInternational capacity on our autonomous system
Mumbai — DubaiPlannedNot lit yet — on the plan
London — AmsterdamPlannedNot lit yet — on the plan
US West — US EastPlannedNot lit yet — on the plan
London — US EastPlannedNot lit yet — on the plan
Singapore — TokyoPlannedNot lit yet — on the plan
Singapore — SydneyPlannedNot lit yet — on the plan
US East — São PauloPlannedNot lit yet — on the plan
Dubai — JohannesburgPlannedNot lit yet — on the plan
FIBER

Routes we own

Fiber pairs between our points of presence in Delhi, Mumbai and Chennai, so the path from our racks to the exchanges is ours — latency, capacity and maintenance windows decided by us.

Delhi – MumbaiMumbai – ChennaiOwn pairs
DATA CENTERS

Joy DC Mumbai · Joy DC Noida

Two data centers of our own under construction, on our fiber, next to the exchanges: racks, power and cooling we design, interconnection on the floor, the platform lit as one more region the day they open.

Under constructionOn our fiberInterconnection inside
PATH

How traffic flows

Every flow is analysed in real time at the border → our backbone → our fabric → exchanges and peers. RPKI-invalid routes are dropped at every border; prefix filters are rebuilt nightly.

RPKI ROAsIRR filters nightlyIPv4 + IPv6BGP communities
PEERING

Open policy

Present at exchanges in India, Southeast Asia and Europe. Bilateral sessions preferred above 1 Gbps; route servers otherwise. The peering portal has the whole guide.

Open policyDirect sessionsdocs.joy.services/peering
04 Hardware
What your server runs on

Enterprise metal, owned outright.

Compute
Joy Compute Fabric dedicated CPU share per server
Processors
Xeon Gold · AMD EPYC enterprise-grade nodes
Memory
ECC on every node
Storage
NVMe redundant on every node
Uplinks
10 / 25 / 100 G per node
Live stats
every 15 s per server
05 Protection
Always on

DDoS scrubbing is a property of the network.

DETECTION

Real-time anomaly scoring

Joy's traffic analysis scores flow anomalies as they happen on every border router.

DIVERSION

Equal diversion to scrubbing

Affected prefixes are diverted to the scrubbing centre automatically, with no phone call; the address stays reachable while the attack is dropped.

COVERAGE

Every port, no traffic cap

Volumetric floods, amplification, SYN/ACK storms and L7 request floods, on every VPS, dedicated server and colocation port.

ELSEWHERE

Virtual Connect

Prefixes hosted anywhere are protected over a GRE tunnel with BGP; clean traffic is delivered to your router.

06 Network contacts
ContactAddressHours
NOCchanderparkash@joycloud.services24/7
Peeringdocs.joy.services/peering · support@joycloud.servicesSessions turn up within a few business days
Abusesupport@joycloud.servicesAcknowledged automatically, reviewed within one business day
Securitysupport@joycloud.servicesAcknowledged within 48 hours
Next step

Latency decides. Deploy where your users are.