Summary

  • The only public trace of Cork Internet Exchange Limited retained in this evidence generation is a RIPE NCC member-directory row carrying the address Unit 8, Hollyhill Industrial Estate, T23 R68N, Cork; no autonomous system, announced prefix, member port, switching platform or facility attributable to the company was retained alongside it.
  • RIPE NCC membership is the gate through which an organisation may request IPv6 address space and AS Numbers; it is an eligibility record, and a reader deciding whether a peering point exists in Munster cannot use it as one.

A company called Cork Internet Exchange Limited sits in the RIPE NCC's public member directory. The name asserts an exchange. The record asserts a membership. Those are different objects, and the distance between them is where this article lives.

The directory entry is short enough to quote in full. It carries the organisation's name and an address: Unit 8, Hollyhill Industrial Estate, T23 R68N CORK IRELAND (RIPE NCC member directory, retrieved 4 November 2026). That is the whole of it. No autonomous system number, no prefix, no switch, no port count, no member list, no peering LAN, no facility floor. A postal address on an industrial estate on the north side of Cork city is a real thing; it is not an interconnection fabric.

I want to be exact about what this finding is, because the temptation in a piece like this is to inflate a thin record into a scandal. It is not a scandal. It is a category error waiting to happen, and the category error is what deserves the column inches.

What a membership row actually buys

The RIPE NCC is not coy about what membership is for. Its own page on managing IPs and ASNs states the condition plainly: "If your organisation needs IPv6 address space and AS Numbers, and/or makes assignments to End Users or customers, you should become a RIPE NCC member" (RIPE NCC, managing IPs and ASNs, retrieved 4 November 2026).

The same page describes what comes with it: the ability to request address space and AS Numbers, access to the LIR Portal for managing those resources, and governance rights including voting at General Meetings and electing the Executive Board. Members are Local Internet Registries. That description reached me as a provider-reported summary of the page rather than a line-by-line quotation, and I am flagging it as such rather than dressing it up as a transcript.

Read that sentence again with a network operator's eye. It says: if you need numbers, join. It does not say: if you join, you have numbers. Membership precedes resources; it does not evidence them. An organisation can hold a membership for years and never request an ASN, or request one and never announce a route, or announce a route and never build a switch, or build a switch and never attract a single peer. Each step in that chain is a separate act with a separate artefact, and the register that records the first step cannot be read as a witness to the fourth.

This matters because the register is where a certain kind of research stops. A name in a directory is easy to cite, easy to search, and easy to mistake for a fact about the world. A switching platform is hard: it needs a room, power, cooling, fibre, optics, a route-server or a peering LAN, and enough counterparties willing to cross-connect to make the whole exercise cheaper than transit. The registry row survives while the fabric may never have existed. That asymmetry is the entire problem with reading infrastructure out of administrative records.

The Munster question

Why does a Cork exchange matter enough to check? Because Ireland's network geography is lopsided, and everyone in the industry knows it without needing a citation. The capital holds the datacentre campuses, the submarine cable landings that feed them, and the country's peering presence. If a genuine second exchange existed in Cork, it would be a meaningful fact: a local peering point for networks in Munster, a shorter path for regional traffic, a bargaining position for operators who currently haul everything to Dublin to hand it over.

So what does the record show about the national layer? In this same generation I retained the home page of the Internet Neutral Exchange Association, which identifies itself as "Internet Neutral Exchange Association", a "Company Limited by Guarantee", at "4027 Kingswood Road, Citywest, Dublin D24 AX06 Ireland" (INEX, retrieved 4 November 2026). That is Dublin, on the western edge of the city, in the middle of the industrial and business park belt where a great deal of Irish network infrastructure is clustered. The country's named peering body gives a Dublin address. Nothing in that footer mentions Cork.

I will not push that observation further than it goes. A footer is a registered office, not a site list, and plenty of exchanges operate from more than one building while keeping one correspondence address. The absence of Cork from a company's footer is not the absence of Cork from its network. What it does establish is narrower and still useful: in the same evidence generation, the only entity in Ireland that publicly presents itself as the country's internet peering point locates itself in Dublin, while the only entity presenting itself as a Cork exchange locates itself in a member directory.

That is the shape of the finding. Not "Cork has no exchange" — I have no basis for that sentence and will not write it. The defensible claim is that from the retained public record, Cork Internet Exchange Limited appears as a membership, not as a fabric, and Ireland's documented peering identity points at the capital.

The honest limits of this check

The obvious next move is to look the company up in PeeringDB, the interconnection database where networks and exchanges record who they are, where they are present and who they peer with. I tried. The retrieval returned a tool error rather than a page. That is a fault in my evidence gathering, not a finding about the database, and the distinction is the sort that too much infrastructure writing quietly elides.

Here is what would settle the question, each item one call away for anyone with a working terminal:

  • A RIPE database object showing an autonomous system number held by the company, with prefixes originated from it.
  • A PeeringDB record for a Cork exchange listing member networks and ports.
  • A facility page or operator statement describing a switching platform at Hollyhill Industrial Estate.
  • An Irish company-registration filing whose objects describe operating an exchange rather than merely holding a name.
  • An INEX or third-party page naming a Cork point of presence as part of the national fabric.

None of those arrived in this generation. Three to four of my retrieval attempts failed at the provider layer with permission or capacity errors, which means the surviving evidence is incomplete by retrieval rather than by the world. I am stating that plainly because the alternative is worse: a piece that treats a failed query as a negative result, and then invites readers to draw a conclusion the evidence cannot carry.

What the record does say

Within those limits, several things are established and worth naming.

The company exists in an authoritative registry, with an Irish address in a Cork industrial estate. Its legal form is recorded in BTW's directory card as a private company, with Ireland as its home country — a card that also carries an unusually candid set of data gaps, instructing that ASN and IP resources be mapped from delegation and routing data before anyone makes a footprint claim (BTW directory entry Only for Strategic Circle). That instruction is the right one, and it is the reason this article is a negative finding rather than an inferred one.

The name uses the standard vocabulary of interconnection. That is not nothing. Naming a company after a facility that does not yet exist is a common, legitimate and occasionally optimistic act: it reserves the concept, it signals intent to partners and investors, it can front a planning application or a funding round. Ireland has seen plenty of announced infrastructure that arrived years after its name did. A name is a claim about the future as often as a description of the present.

And the registry itself is doing exactly what it was designed to do. It lists members. It is not a facility register, it has never pretended to be, and the fact that a reader can mistake one for the other is a problem with the reader, not the registry.

Why operators should care anyway

The practical stake is not abstract. A regional ISP in Munster, a content network weighing where to place a cache, a datacentre developer sizing a connectivity package, an investor doing diligence on an Irish operator: all of them periodically encounter a name like this one and have to decide what it is worth. The lazy answer is to assume a company named after an exchange runs one. The expensive answer is to check, and the check takes about as long as reading this paragraph.

What the check reveals here is a familiar pattern in second-tier network markets. The capital accumulates the fabric; the regions accumulate the names. Cork is Ireland's second city by population and a genuine industrial base, with a long history in pharma, semiconductors and software. It has the density to justify local interconnection on paper. Whether it has the traffic to justify it in practice is a question only measured port counts and peering volumes can answer, and neither was available to me.

So the correct posture for an operator reading the registry row is neither dismissal nor belief. It is a short list of follow-ups: does the entity announce anything, does it appear in an interconnection database, does it name a facility, does anyone peer with it. Until those come back affirmative, a Cork port is a hypothesis, and a hypothesis is a poor basis for a capacity plan.

The dated conclusion

As of 4 November 2026, the retained public record for Cork Internet Exchange Limited consists of a RIPE NCC membership listing, a Cork postal address, and the name itself. Ireland's identified peering presence in the same generation sits at Citywest in Dublin. No autonomous system, announced prefix, member network, switching platform or physical facility attributable to the Cork entity was retained, and a PeeringDB query failed on the tool side rather than returning an empty result.

That is the finding, and it is worth publishing precisely because it is thin. The infrastructure record is full of names that outrun their networks. The discipline is to say which one you are looking at: a corporation with a registry account, or a place where packets meet. On the evidence I could hold in my hands, Cork Internet Exchange Limited is the first. Whether it ever becomes the second is a question with an answer, and the answer lives in routing tables, not in a directory.

Until someone produces it, the honest description of Cork's internet exchange is a name, an address, and a membership number.