ixreport

LIONET ONLINE

AS133591 · LioNet

LIONET ONLINE PVT LTD

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
4Facilities in PeeringDB

Tools: Where can I peer with LIONET ONLINE? · Where should LIONET ONLINE peer next? · Compare LIONET ONLINE with another network

This network elsewhere: the registry history of AS133589-AS133598, the block AS133591 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in LIONET ONLINE's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on LIONET ONLINE'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 Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB2401:7500:fff6::3b is AS134325 Jetspot Networks2401:7500:fff6::3b
    Port speed differs10G3G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 103.27.171.166: set Speed to 3000 (3G) (now 10000).

Exchanges over time

012Oct 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, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where LIONET ONLINE'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 10G across 1 exchange.

India DE-CIX Mumbai Mumbai, India 103.27.171.166 10G Yes Both Address takenSpeed differs

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

These exchanges have a switch in a facility where LIONET ONLINE lists itself in PeeringDB, but don't have LIONET ONLINE 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.

Facilities (4)

The buildings LIONET ONLINE lists in PeeringDB, and how many of the exchanges in each it's on.

India Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai 1 of 7
India Sify Greenfort - NoidaNoida 0 of 7
India TATA Communications MumbaiMumbai 1 of 2
India Equinix MB3 - MumbaiMumbai 1 of 1

Recent changes Search them

  • Oct 13, 2026 [PDB] AS133591 LIONET ONLINE left Extreme IX Mumbai
  • Oct 12, 2026 [IXF] AS133591 LIONET ONLINE dropped from Extreme IX Mumbai's IX-F list (still in PeeringDB)
  • Oct 8, 2026 [PDB] AS133591 LIONET ONLINE now in PeeringDB at DE-CIX Mumbai
  • Oct 8, 2026 [PDB] AS133591 LIONET ONLINE now in PeeringDB at Extreme IX Mumbai
  • Oct 8, 2026 [PDB] AS133591 LIONET ONLINE no longer in PeeringDB at Extreme IX Mumbai (still on its IX-F list)