Summary

  • The RIPE organisation object ORG-MDMG3-RIPE names Microsoft Deutschland MCIO GmbH, quotes Handelsregister HRB 218697, and still prints the Unterschleißheim street address the company's registered seat left in October 2016.
  • AS200517, assigned to that same organisation, is reported as originating no prefixes at all, while the /15 covering its legacy space is announced by AS8075 under a ROA whose maximum length is /15 — which authorises the /15 itself and nothing longer.

The name on the register

The RIPE NCC member directory lists Microsoft Deutschland MCIO GmbH under Germany, address Konrad-Zuse-Straße 1, 85716 Unterschleißheim, areas serviced "DE – GERMANY". The page prints a name, a street and a service area. It does not print the organisation identifier, the AS number or the register number.

One rung down, the organisation object does. ORG-MDMG3-RIPE carries org-name Microsoft Deutschland MCIO GmbH, country DE, reg-nr: District court München HRB 218697, org-type: LIR, the same Unterschleißheim address, abuse-c MAC274-RIPE and two maintainers, RIPE-NCC-HM-MNT and MICROSOFT-MAINT, as reproduced in a RPSL mirror. A second whois mirror dates that object's creation to 2015-06-12 and its last modification to 2026-05-13; older cached copies of the same object carry 2016-10-06 and 2022-03-08.

The register number is where the chain starts to bend. The German commercial register holds that company at Amtsgericht München, HRB 218697, active, with a business address at Walter-Gropius-Straße 5, 80807 München, and it reproduces the move: a shareholders' resolution of 19.10.2016 amending §1 of the articles, entered on 28.10.2016, seat from Unterschleißheim to Munich, per the register excerpt. A second register aggregator states the same seat, the same street address and the same HRB number. My arithmetic: nine days from resolution to entry, and roughly ten years and one month from that entry to today.

So the RIPE object names the correct legal person, quotes the correct register number, and prints an address that has been the wrong one since 28 October 2016 — inside an object that was modified in 2026. The field is maintained. The value is historical. No register reports that mismatch anywhere; a reader assembles it from two documents that never cite each other.

The status field that cannot divide a range

The two legacy ranges under this organisation carry status: LEGACY, as reproduced in a RIPE whois copy. RIPE's own documentation is unusually direct about what that word can and cannot mean:

'LEGACY' - These are resources that were allocated to users before the RIPE NCC was set up.

and, in the same object-type documentation:

The whole legacy hierarchy shares the LEGACY status, so sub-allocations and assignments cannot be distinguished by status.

The combined database documentation repeats the definition — resources distributed before, or outside, the current system of hierarchical distribution by the regional registries, transferred from IANA's central registry according to the location of their legal organisation contact at the time. None of that is a statement about who operates the addresses.

The object reads 51.4.0.0 – 51.5.255.255, netname MICROSOFT, country DE, org ORG-MDMG3-RIPE. My arithmetic: 131,072 addresses. A second object reads 51.8.0.0 – 51.8.255.255: 65,536 addresses. The two named ranges come to 196,608 addresses, a floor on recorded custody rather than an inventory — the complete list of inetnum objects under ORG-MDMG3-RIPE was not obtained for this piece.

An assigned AS number and nothing to announce

AS200517 carries as-name MS-DEUTSCHLAND, org ORG-MDMG3-RIPE, admin-c DH5902-RIPE, tech-c MRPA3-RIPE, status: ASSIGNED, created 2015-06-17 and last modified 2024-04-23. The status attribute is generated by the registry, and RIPE's 2012-07 implementation note states what it means:

This attribute will automatically be set to "ASSIGNED" for all AS Number resources assigned by the RIPE NCC, "LEGACY" for all legacy AS Numbers, and "OTHER" for copies of AS Number resources assigned by other RIRs that have been added to the RIPE Database for routing purposes.

Users cannot modify or delete it. ASSIGNED therefore attests exactly one thing: that the RIPE NCC assigned this AS number to this organisation. It attests nothing about prefixes. RIPEstat's own resource page names Microsoft Deutschland MCIO GmbH as holder with status ASSIGNED and reports no prefixes originated or transited in RIS.

The outside readings agree, and the disagreement inside them is the story. One BGP tool's AS view records the name, the 17.06.2015 registration, the line No prefixes announced, and a withdrawal of 51.4.0.0/16, 51.5.0.0/16 and 51.18.0.0/16 at 21.10.2026 12:21. My arithmetic: 21 October to 20 November 2026 is thirty days.

The same tool's page for 51.4.0.0/16 is more interesting than a zero. It marks the prefix RPKI invalid (origin) and Not announced, and prints the covering authorisation: 51.4.0.0/15, maximum length /15, origin AS8075, RIPE trust anchor. A route origin authorisation with maxLength /15 authorises one prefix length and one only — the /15 itself (my arithmetic). An announcement of the more specific /16 with origin AS200517 sits outside that authorisation by construction. It is invalid whether or not anyone ever sends it.

A second routing toolkit shows what is carrying the space: 51.4.0.0/15 announced by origin AS8075 Microsoft Corporation, prefix registrant Microsoft Deutschland MCIO GmbH, with an IRR route object 51.4.0.0/15 origin AS8075 maintained by MAINT-AS8075 and modified 2024-03-13.

Put two fields side by side and the article is there. The registrant field says Microsoft Deutschland MCIO GmbH, a Munich company with HRB 218697. The origin field says AS8075. A reader who takes the registrant field for the operator gets a German GmbH; the packets come from a network the register files under a different handle. Neither field is wrong. They answer different questions.

Three names, two register numbers

Microsoft's German-language imprint names the provider "im Sinne des § 5 DDG" as Microsoft Corporation, One Microsoft Way, Redmond, with a Universal Business Identifier of 600 413 485, per the imprint page. A separate Microsoft Germany imprint names Microsoft Deutschland GmbH, Amtsgericht München HRB 70438, as provider for certain German offers. The imprint excerpts read for this piece do not name Microsoft Deutschland MCIO GmbH at all.

Two German companies, two register numbers: HRB 70438 and HRB 218697. A US corporation behind the website notice. And the RIPE registrant, MCIO, which appears in the registry documents and in none of the provider notices read.

I will not invent the missing page. Across the documents read here, no single one carries the chain from the imprint's provider to the registry's registrant to the routing table's origin. The registry separates custody from routing by design. The company's notices separate the website from the German offers. The routing table separates registrant from origin. Three separations, all documented, none bridged.

What to ask, and of which document

If the question is who holds custody of 51.4.0.0/15 as the registry records it, ORG-MDMG3-RIPE answers: MCIO under HRB 218697, with an address that needs updating and a LEGACY status that cannot subdivide the range.

If the question is whose network carries the packets, the answer is AS8075, and the authorisation that makes that announcement valid names AS8075 alone.

If the question is which company operates the German block — runs the infrastructure, signs for the circuits, answers for the addresses — no document read here prints it. That is the gap this piece documents, and it is the gap a due-diligence file is most likely to paper over with the registrant field, because the registrant field is the one carrying a company name.

Reading limits

No live authoritative RIPE Database response was read: the web query interface rendered no readable text to the tooling used here. Organisation, aut-num and inetnum values rest on mirrors that reproduce RPSL output plus RIPEstat's summary, and are reported as such throughout. The organisation object has been edited more than once; a single last-modified date does not describe its state. The official Handelsregister extract was not inspected: seat, street address and register number rest on a commercial register portal and one aggregator, both secondary. The non-announcement and withdrawal readings come from a single collector vantage, and RIPEstat reporting nothing originated is corroboration from a different dataset, not the same measurement. Whether a RIPE route object exists for 51.4.0.0/16 with origin AS200517 was not settled; the authoritative whois endpoint sat outside what this route could read.

Start here: the BTW directory entry for Microsoft Deutschland MCIO GmbH.