ixreport

HOTARU NETWORK

AS200455

HOTARU NETWORK LTD.

12Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
11Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

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

Make the changes on HOTARU 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. United States CXIX - Great Lakes NewYork, United States · PeeringDB 4721
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone33.0.0.67
    • In the entry with IPv6 2a0f:7803:fc60:aaaa::2004:55: set IPv4 to 33.0.0.67 (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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.174
    • In the entry with IPv6 2001:7f8:aa::174: set IPv4 to 185.0.24.174 (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

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

Map

Where HOTARU 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 56.1G across 12 exchanges.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:f07:1 1G Yes Both
Germany 91-IX Frankfurt, Germany 2001:7f8:1a:91::86 10G Yes PeeringDB
United States CXIX - Great Lakes NewYork, United States 2a0f:7803:fc60:aaaa::2004:55 10G Yes Both IPv4 not in PeeringDB
Netherlands IXP NL DRO Dronten, Netherlands 2001:7f8:d0:4e4c:0:3:f07:1 1G Yes PeeringDB
Japan Japan Community IX Japan, Japan 202.226.3.38 2402:b7c0:e000::20:455:1 1G PeeringDB
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::174 10G Yes Both IPv4 not in PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 185.1.167.206 2001:7f8:f2:e1:0:20:455:1 1G Yes PeeringDB
United States MoeIX SEA Seattle, United States 2a0a:280:f000:3:0:20:455:0 1G Yes PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::cc 100M Yes Both
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::16 10G Yes PeeringDB
Italy SIIX Pomezia Pomezia, Italy 185.1.206.15 2001:7f8:112::15 1G Yes PeeringDB
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:20:455:1 10G Yes PeeringDB
Facilities (1)

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

United Kingdom Vinters ConnectMaidstone 1 of 1