ixreport

Sathya Web Services

AS139484 · SATHYA WEB SERVICES

Sathya Web Services Private Limited

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Sathya Web Services? · Where should Sathya Web Services peer next? · Compare Sathya Web Services with another network

This network elsewhere: the registry history of AS139477-AS139576, the block AS139484 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Sathya Web Services's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Sathya Web Services's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.228.174.22 103.228.174.25103.228.174.22
    IPv6 address in PeeringDB, not in the export2400:d180:68::22 2400:d180:68::252400:d180:68::22
    Port speed differs2 × 10G2 × 10G + 2 × 5G + 3G
    • The entry with IPv4 103.228.174.25, IPv6 2400:d180:68::25 isn't in the export: delete it if that connection is gone.

Exchanges over time

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where Sathya Web Services's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 20G across 1 exchange.

India DE-CIX Chennai Chennai, India 103.228.174.22
103.228.174.25
2400:d180:68::22
2400:d180:68::25
2 × 10G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs

Exchanges in its buildings that it isn't on (2)

These exchanges have a switch in a facility where Sathya Web Services lists itself in PeeringDB, but don't have Sathya Web Services as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

India Extreme IX ChennaiChennai, India 91 Bharti Airtel Santhome; STTGDC CHN1
India NIXI ChennaiChennai, India 56 Bharti Airtel Santhome; STTGDC CHN1
Facilities (2)

The buildings Sathya Web Services lists in PeeringDB, and how many of the exchanges in each it's on.

India Bharti Airtel SanthomeChennai 1 of 3
India STTGDC CHN1Chennai 1 of 3