ixreport

Xkrme Network

AS199018

Xkrme Network LLC

2Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
2Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Xkrme Network? · Where should Xkrme Network peer next? · Compare Xkrme 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 Xkrme Network's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in Xkrme Network's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom Kent Internet Exchange Point Kent, United Kingdom · PeeringDB 4316From its IX-F export
    IPv4185.0.24.192
    IPv62001:7f8:aa::192
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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. Japan TYIX Tokyo, Japan · PeeringDB 4866
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone23.154.164.178
    • In the entry with IPv6 2602:f429:31::33: set IPv4 to 23.154.164.178 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20261
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
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

In the last 30 days Xkrme Network joined 1 exchange and left 0. Growing networks

Joined

  • TYIX Tokyo Oct 31, 2026

Map

Where Xkrme 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 11G across 2 exchanges.

United Kingdom Kent Internet Exchange Point Kent, United Kingdom 185.0.24.192 2001:7f8:aa::192 10G Yes Not in PeeringDB
Japan TYIX Tokyo, Japan 2602:f429:31::33 1G Yes Both IPv4 not in PeeringDB

Xkrme Network lists no facilities in PeeringDB.

Recent changes Search them

  • Nov 1, 2026 [PDB] AS199018 Xkrme Network no longer in PeeringDB at Kent Internet Exchange Point (still on its IX-F list)
  • Nov 1, 2026 [PDB] AS199018 Xkrme Network now in PeeringDB at TYIX
  • Oct 31, 2026 [IXF] AS199018 Xkrme Network added to TYIX