ixreport

Pmman Network

AS219332 · Pmman Network

Pmman

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Non-ProfitType
OpenPeering policy
4Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Pmman Network? · Where should Pmman Network peer next? · Compare Pmman Network with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Pmman Network's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Pmman Network'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 (2)

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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.227
    • In the entry with IPv6 2001:7f8:aa::227: set IPv4 to 185.0.24.227 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Japan TYIX Tokyo, Japan · PeeringDB 4866
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone23.154.164.159
    • In the entry with IPv6 2602:f429:31::20: set IPv4 to 23.154.164.159 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where Pmman Network'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 31G across 4 exchanges.

Germany 91-IX Frankfurt, Germany 2001:7f8:1a:91::82 10G Yes PeeringDB
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::227 10G Yes Both IPv4 not in PeeringDB
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::98 10G Yes PeeringDB
Japan TYIX Tokyo, Japan 2602:f429:31::20 1G Yes Both IPv4 not in PeeringDB
Facilities (1)

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

United Kingdom Vinters ConnectMaidstone 1 of 1

Recent changes Search them

  • Oct 8, 2026 [PDB] AS219332 Pmman Network left ixFabric - Hong Kong
  • Oct 8, 2026 [PDB] AS219332 Pmman Network left ixFabric - Tokyo