Q-MEX Networks shows why a live ASN is still not enough to call an ISP

Summary

• Q-MEX Networks GmbH has live network-resource evidence: AS211664 is assigned in RIPE, RIPEstat showed the ASN announced on July 9, 2026, and the public routing view included four IPv4 /24s and one IPv6 /48.
• The company also presents itself as a German managed IT, cloud, backup, security and telephony provider; its own status page lists Internetanschluesse (Q-LINE), Netzwerk und Routing, Q-IaaS, Online Backup, Hosted Exchange, Telefonie and data-centre labels as monitored services.
• That combination makes Q-MEX a real network-adjacent infrastructure operator, but it is not enough to classify the company as a public regional ISP without visible tariffs, service terms, customer access footprints or regulator-grade access-market evidence.
• The most useful market reading is therefore not "inactive" and not "consumer ISP"; it is a small German service provider whose autonomous-system, LIR and hosted-service posture could support business connectivity, hosted infrastructure or managed-service differentiation if public commercial proof deepens.

A small German operator with a bigger evidence problem

Q-MEX Networks GmbH sits in an awkward but important part of the communications market. It is not one of the giant carriers whose networks are visible through national coverage maps, spectrum holdings, cable landings, wholesale reports and regulator filings. It is also not a bare legal shell that appears only in a registry and nowhere else. Public evidence places it in the middle: a German company selling managed IT services, cloud-style infrastructure, backup, data-protection, security monitoring and business telephony, while also holding and operating Internet number resources through AS211664.

That middle position matters because small infrastructure providers are often misread in two opposite ways. One mistake is to treat any autonomous system number as proof that the holder is an Internet service provider in the customer-access sense. Another mistake is to dismiss a small ASN as dormant or irrelevant if it does not look like a mass-market ISP. Q-MEX is a useful case because current public data pushes against both shortcuts. AS211664 is not merely allocated; RIPEstat showed it announced on July 9, 2026. Q-MEX's status page is not a generic corporate brochure; it names network and routing, Internet connections, virtual infrastructure, hosted exchange, online backup, telephony and two data-centre service labels. At the same time, the public web does not show a consumer broadband tariff book, a clear regional access map, installation and fault terms, wholesale service descriptions, or enough public customer evidence to place the company confidently in the regional ISP category.

The right reading is narrower and stronger. Q-MEX appears to be a managed-service and business-infrastructure provider with its own or directly managed network-resource layer. That layer gives it optionality. It can host customer workloads behind address space it controls. It can run mail, backup, SIEM, firewall, telephony and virtual infrastructure services with more autonomy than a pure reseller. It can peer or buy transit under its own routing policy. It can present business Internet access as part of a service bundle. But optionality is not the same thing as market proof. For a reader trying to understand where Q-MEX fits in the infrastructure economy, the important question is not whether the company has a network identifier. It does. The important question is what public evidence shows the network being monetised as a service.

The answer is mixed. Q-MEX's own site says it has been working for customers for 20 years on communications paths and complex IT processes in secure environments. Its About page says the team has more than 15 employees, has IT partners, works around Internet and network technology, and has servers at three locations in Germany. Its service pages describe firewall work, Seafile infrastructure, cloud services, IT outsourcing, Veeam-based managed backup, Q-SIEM, hosted e-mail, Exchange and innovaphone telephony. The home page even uses the label "Highspeed Internet" and says Q-MEX offers reliable Internet and cloud telephony. These are not the signs of an empty resource holder. They are signs of a service provider with a technical operating surface.

But the public record still leaves the access-ISP question unproven. The strongest access signal is the status-page service name "Internetanschluesse (Q-LINE)," which translates as Internet connections. It shows Q-MEX monitors an Internet-access service category. The same status page also records a July 4, 2026 maintenance window for an outside-bandwidth upgrade in which the LWLCOM connection was to be expanded to 10 Gbit/s. Those facts support the view that Q-MEX runs production connectivity infrastructure. They do not, by themselves, show who can buy access, what access products are sold, where physical service is available, how faults are handled, or whether access is the first paid unit rather than an add-on to outsourced IT and telephony accounts. For classification, that distinction is decisive.

What the company says it sells

Q-MEX's public website frames the company as a smart IT and communications provider for business customers. The home page promotes business telephony, cloud and network IT, IT outsourcing, backups and data protection. It says the company helps manage complex IT processes in a secure environment and wants to give end users strong usability. The same page presents customer-facing propositions rather than a carrier-style network footprint: cloud telephony, backups as a rescue anchor, firewall-based security and professional IT services.

The Cloud and Network IT page is especially useful because it links the company's IT-service identity to hosted infrastructure. It asks whether the customer's IT devices can communicate with one another, whether a phone system can work with PCs, whether firewalls can work with VPN and backup, and whether all of that can work with the cloud. The page says Q-MEX makes networks smart and enables work from office, home, abroad and other locations. More specifically, it says Q-MEX provides infrastructure for Seafile, discusses cloud-based backups, and offers access to separate company-owned infrastructure through various cloud services. That is not a mass-market access catalogue. It is a business IT integration claim, built around managed networks, firewalling, collaboration, cloud services and backup continuity.

The IT outsourcing page strengthens that interpretation. It offers Q-MEX as a service provider that can take over server environments, server management, software support, software development, cloud telephony, backup, maintenance and network support. It also refers to proactive monitoring, SLAs, high availability, protection against cyber crime and risk reduction. For a small German provider, this is a familiar MSP pattern: the customer is not simply buying an access line; the customer is outsourcing an operating responsibility. Network support is part of a broader bundle, and the bundle is aimed at small and mid-sized organisations that do not want to run every IT function in-house.

The backup page pushes Q-MEX further into hosted-infrastructure territory. It presents managed backup services based on Veeam, says backups are stored in redundant data stores in Germany, and discusses Veeam Cloud Connect, Microsoft 365 backup, backup as a service and disaster recovery as a service. That language matters because it implies storage, data movement, restore processes and service-level responsibility. A provider offering backup repositories and DRaaS benefits from reliable routing, address control and data-centre connectivity. The network layer may not be the product headline, but it becomes part of the trust proposition.

The security pages add another layer. Q-MEX's Q-SIEM page describes real-time monitoring, threat intelligence, compliance support, automated security reactions, centralised security-event views, reporting, anomaly detection, incident response, forensics and SOAR-style workflows. The data-protection and secure e-mail pages describe firewalling, encrypted exchange, MXGate, Exchange and advice around data processing and GDPR-compliant security. These services need stable infrastructure, but they are not telecom access products. They point to a managed-security and managed-communications business that can sit above, beside or bundled with connectivity.

The telephony page is the one most clearly adjacent to public network service. Q-MEX promotes innovaphone-based cloud telephony, says the solution can be offered with connection included, and mentions availability in Germany, Austria and Switzerland. Combined with the home page's high-speed Internet blurb and the status page's Q-LINE label, this creates a plausible business-connectivity thesis. Q-MEX may offer Internet access and telephony as a bundle for business customers. Yet the public page still reads as a consultative business service, not a published carrier tariff. For market classification, that means the evidence supports "business IT and network services" more cleanly than it supports "regional ISP."

The network-resource layer is real

The strongest hard evidence around Q-MEX is not marketing copy. It is the RIPE and routing record around AS211664. RIPE's organisation object ORG-QNG1-RIPE names Q-MEX Networks GmbH, country DE, registration reference "District court Walsrode HRB 206998," organisation type LIR, and an address in Achim, Germany. The same RIPE organisation record has a creation timestamp in 2019 and a last-modified timestamp in May 2026. The official company Impressum, meanwhile, gives Q-MEX Networks GmbH, managing director Markus Plischke, Hansastrasse 86, 27751 Delmenhorst, phone number, e-mail address and German VAT identifier. The address difference is not unusual for small companies with corporate, operational or registry contact points, but it is a reminder that number-resource data and legal imprint data answer different questions.

The aut-num object for AS211664 names the AS as QMEX and links it to ORG-QNG1-RIPE. It is marked assigned. Its import and export lines name three upstream relationships in routing-policy form: AS50629 for LWLCOM, AS174 for Cogent, and AS8220 for COLT. The status page's July 2026 maintenance item independently reinforces at least one of those names: it says a connection to LWLCOM was being expanded to 10 Gbit/s. This is an important cross-check. A stale routing-policy object can overstate reality if it is not matched by observed routes or operational notices. In Q-MEX's case, the RIPE policy record, the RIPEstat observed routes and the status-page maintenance note all point in the same direction: AS211664 is part of a live connectivity stack.

RIPEstat's routing-status data on July 9, 2026 showed AS211664 announced, with four IPv4 prefixes totalling 1,024 IPv4 addresses and one IPv6 /48. Its visibility numbers were high: the data showed hundreds of RIS peers seeing the routes in both IPv4 and IPv6. RIPEstat's announced-prefixes endpoint listed 91.232.22.0/24, 91.232.23.0/24, 185.226.241.0/24, 185.226.242.0/24 and 2a12:84c0:1::/48 in the recent timeline. Those are not the numbers of a national network, but they are large enough for real business services, hosted systems, customer edge assignments, backup infrastructure, mail services, security platforms or telephony systems.

The route objects add historical shape. The 185.226.241.0/24 route object for AS211664 was created in May 2023. The 91.232.22.0/24 route object was created in June 2023. The 2a12:84c0:1::/48 route6 object was also created in June 2023. RIPE allocation objects show 91.232.22.0 - 91.232.23.255 under netname DE-QMEXGMBH-20191003 and 185.226.240.0 - 185.226.243.255 under netname DE-QMEXGMBH-20171019, both with Q-MEX's RIPE organisation attached. In other words, this is not merely a one-off borrowed announcement. Q-MEX has an address-resource history and a routing setup that has been evolving across several years.

PeeringDB gives a softer but still useful view. The public PeeringDB entry for ASN 211664 lists the network name as QMEX, links to the Q-MEX website, lists a general open peering policy, includes IRR AS-SET AS211664:AS-QMEX, and reports no listed IX LAN or facility records in that entry. It also shows prefix counts. PeeringDB data is participant-maintained and should be read as a network-operator profile, not as regulator proof. But it helps locate Q-MEX in the network-resource ecosystem: the company has an ASN profile, a website, an IRR set, and a stated policy, while not exposing a broad public peering fabric through that profile.

The negative evidence is just as important. The public routing evidence does not show end users. It does not show customer contracts. It does not prove a fibre footprint, cable plant, DSL resale arrangement, wireless access network or municipal coverage area. It does not show that Q-MEX's address space is delegated to retail access customers rather than used for hosted services, internal infrastructure, cloud platforms, mail, telephony or managed firewalls. ASN evidence tells us that Q-MEX originates and routes prefixes. It does not tell us what product line creates the revenue.

Why an ASN is not an ISP label

An autonomous system number is a routing identity. It lets a network express routing policy, originate prefixes, receive transit, peer, and participate in the global BGP system. Many access providers have ASNs, but many non-access providers also have ASNs. Hosting firms, managed-service providers, enterprise networks, SaaS operators, universities, payment firms, government agencies, exchanges, content platforms and security companies can all run autonomous systems. The ASN answers the question "who is originating this route?" It does not answer the question "what retail service does the holder sell?"

That distinction is especially important in the German mid-market. A service provider can sell managed backup, virtual servers, hosted e-mail, security monitoring, firewalling, VoIP and IT outsourcing without being a public access ISP. It can also sell business Internet access as part of those services without looking like a mass-market ISP. A customer may see one invoice for outsourcing, telephony, hosted infrastructure and connectivity. Public routing observers may see the provider's ASN. Neither view alone proves the market category.

Q-MEX's evidence fits that hybrid zone. The company calls itself a service provider. Its pages repeatedly emphasise customer advice, managed service, cost reduction, support, monitoring, high availability and outsourced operation. The network is visible, but it is rarely presented as a standalone access network. The exception is "Highspeed Internet" on the home page and "Internetanschluesse (Q-LINE)" on the status page. Those access signals should be taken seriously. They show that Internet access is in the operating vocabulary. The classification still needs stronger public proof before it becomes the lead identity.

A stronger regional-ISP case would include several additional pieces of public evidence. It would show named Internet access products with speeds, recurring prices or quote structures. It would describe service areas, installation terms, router handoff, fault handling, SLAs, business-continuity options, and possibly wholesale or last-mile dependencies. It might include regulator registration, procurement awards, public customer access references, network maps, local-news coverage, IX presence, or facility listings. Q-MEX may have some of this privately in proposals or contracts, but the public evidence reviewed here does not show enough of it.

The result is not a downgrade in importance. It is a better definition of importance. Q-MEX is relevant because it illustrates how a small German business-infrastructure provider can operate real network resources without becoming easy to classify from the outside. For market analysts, that is precisely the point. Network-resource evidence can reveal capabilities before commercial evidence reveals product scale. It can show that a company has built the technical basis for resiliency, address control, transit choice and hosted service independence. It cannot turn that basis into an access-market claim by itself.

The operating surface behind the routes

The status page is the clearest window into Q-MEX's live operating surface. On July 9, 2026, the status API returned Q-MEX Networks Status as operational. The rendered status page and its embedded data listed monitored services including Website, 3CX, AntiSPAM (MXGate), Hosted Exchange, Internetanschluesse (Q-LINE), Online Backup, Telefonie, Virtuelle Infrastruktur (Q-IaaS), RZ BRE01, RZ DEL01, and Netzwerk und Routing. The grouping of those services is instructive. Q-MEX is not monitoring only a website and an office phone line. It is monitoring service categories that map to hosted infrastructure, communications, mail, backup, connectivity, routing and data-centre operations.

The July 4, 2026 maintenance window is even more specific. It covered 3CX, AntiSPAM, Hosted Exchange, Internet connections, network and routing, online backup, both data-centre labels, telephony, virtual infrastructure and website service. The description said Q-MEX would perform planned work on one of its Internet connections and expand the LWLCOM connection to 10 Gbit/s. That is a concrete operating fact. It ties one of the RIPE aut-num upstream names to an operational maintenance event and to capacity expansion. It also suggests that the network layer touches multiple service categories, because the maintenance window affected a broad set of monitored services.

The data-centre labels are not full facility disclosures. RZ is a common German abbreviation for Rechenzentrum, or data centre. BRE01 likely points toward Bremen and DEL01 toward Delmenhorst or a related operational naming convention, but the public page does not define the locations in detail. The About page says Q-MEX's servers are positioned at three locations in Germany and references 24/7 emergency availability, redundancy, professional service and a 24-hour service orientation. The status page lists two data-centre labels. These facts support a hosted-service reading, but they do not prove ownership of physical data-centre facilities or a broad colocation business.

The service list also helps explain why address space matters. Hosted Exchange, MXGate, SIEM, backup repositories, virtual infrastructure and telephony systems all benefit from stable addressing, routing autonomy and predictable upstream arrangements. A managed-service provider that controls its own BGP announcements can make routing and failover decisions that a pure white-label reseller cannot. It may improve mail reputation management, firewall policy, VPN endpoints, backup ingress and egress, customer segmentation, DDoS handling or provider redundancy. None of that requires a public broadband footprint.

Q-MEX's routes are therefore best read as infrastructure-enabling evidence. They show that the company has a network substrate capable of supporting the managed services it advertises. They do not show the revenue mix. The operating surface could be monetised through outsourced IT contracts, managed backup, hosted telephony, hosted e-mail, virtual infrastructure, security monitoring, business Internet access or some combination. The market signal is that Q-MEX has moved beyond being a consultant with partner portals and into running identifiable network infrastructure.

Substitutes and alternative explanations

Several substitute theses compete with the regional-ISP reading. The first is active MSP with owned network resources. This is the strongest public thesis. It fits the service pages, the status page, the RIPE LIR record, the ASN, the prefixes, and the hosted-service language. Under this model, Q-MEX uses its autonomous system to support cloud, backup, telephony, e-mail, security and outsourced IT customers. Connectivity may be part of the bundle, but not necessarily the primary paid unit.

The second is business connectivity provider. The home page's Highspeed Internet language, the status page's Q-LINE Internet connections, the telephony page's "connection included" statement, and the routing setup all support this possibility. It may be that Q-MEX sells Internet access to business customers in a targeted, consultative way rather than through a public tariff page. If so, it still may not look like a conventional regional ISP. It would be more like a business IT provider that can include access, voice and cloud in one managed relationship.

The third is hosted infrastructure operator with transit accounts. The Q-IaaS, Hosted Exchange, Online Backup, MXGate, SIEM, backup and server-location evidence support this view. Under this model, address space and upstreams primarily serve Q-MEX's own platforms and customer-hosted systems. The network is production-relevant, but access lines are secondary. The July 2026 LWLCOM upgrade would then be a capacity and resiliency move for hosted services rather than a sign of retail ISP expansion.

The fourth is leased or lightly used ASN service. This is weaker for Q-MEX because the company has multiple supporting signs: LIR status, linked address allocations, a public status page, an upstream maintenance note, service pages that require infrastructure and a PeeringDB entry. Still, observers should not assume every prefix under AS211664 maps to Q-MEX-branded customer service. Some address space could serve internal platforms, partner-hosted systems, customer appliances, backup repositories or third-party service dependencies. The public evidence identifies the routing origin, not every downstream use.

The fifth is inactive or dormant resource holder. Current evidence does not support that as of July 9, 2026. RIPEstat showed announcements, route objects exist, visibility was high, PeeringDB has a network entry, and Q-MEX's own status page described recent bandwidth work. A stale directory or older summary may have described limited impact before visible route announcements appeared or before they were checked. Today, the better description is "live but not fully classifiable as an access ISP."

What would upgrade the thesis

The main upgrade would be public access-product proof. If Q-MEX publishes Q-LINE details with speeds, availability areas, installation terms, router handoff, support commitments, prices or quote categories, the market reading changes. The company would move from "service provider with an access signal" toward "business connectivity provider." If those materials show local or regional coverage and access as the first paid unit, the regional-ISP category becomes more defensible.

The second upgrade would be third-party customer evidence for connectivity. Testimonials on the home page already support customer use of IT services. A connectivity-specific case study, procurement notice, local business reference or service review would be more valuable. The difference is simple: an outsourcing testimonial proves service capability, while an access-specific reference proves that customers buy network access from Q-MEX as a product. The current record has the former more clearly than the latter.

The third upgrade would be facility and interconnection transparency. PeeringDB currently lists no IX LAN or facility records in the public entry seen for AS211664. That does not mean Q-MEX has no facilities or interconnection arrangements; it means they are not exposed there. Facility listings, IX participation, public looking glass data, network maps or route-server visibility would make the peering-and-transit story richer. They would also help distinguish an access network from a hosted-service network.

The fourth upgrade would be regulatory or trade context. A public telecom registration, wholesale access relationship, reseller disclosure, local broadband procurement record or business connectivity award would materially change classification confidence. Germany has many small and medium providers that operate through wholesale layers, business parks, local fibre partners or managed lines. Public records around those arrangements would show whether Q-MEX is participating as a network access provider, a managed-service integrator or both.

The fifth upgrade would be more longitudinal routing evidence. RIPEstat already shows the ASN announced in the current window, route objects from 2023, and high visibility. Ongoing observation could show whether Q-MEX adds prefixes, increases IPv6 use, expands upstream diversity, appears at exchanges, changes AS-SET members, or starts advertising customer cone growth. That kind of change would not prove retail ISP status by itself, but it would show whether the network is scaling beyond a compact hosted-service footprint.

Why the institutional category is the better fit today

The assigned institutional category is appropriate because the public proof is strongest around corporate identity, LIR status, number-resource governance, managed services and business infrastructure. Q-MEX is a real operating company. It has a legal imprint, a RIPE organisation, an ASN, address resources, public service pages and an operational status page. It presents an identifiable business model. But the evidence does not meet the higher bar for an access-provider category where the article would need to show access/connectivity as the first paid unit plus public terms or equivalent proof.

Cloud Service is also plausible but not the best primary category for this article. Q-MEX offers cloud-related services, virtual infrastructure, hosted Exchange, backup, DRaaS language, cloud telephony and infrastructure for cloud services. Those are strong cloud and hosted-service signals. Yet the article's central question is not whether Q-MEX sells hosted IT. It is how to interpret network-resource evidence and why a live ASN does not automatically equal ISP classification. The institutional category gives room to focus on governance, evidence and classification without overstating the product line.

Regional ISP is tempting because of Q-LINE, Highspeed Internet, telephony with connection included, upstream policy and routing visibility. But the evidence still lacks public access tariffs, service areas, installation/fault terms and customer-access documentation. The article should not hide the access signal. It should place it in the right confidence band. Q-MEX may be a business Internet provider for some customers; the public case is not yet mature enough to make that the lead category.

That discipline matters for readers who follow network-resource signals. Small ASNs often become early indicators of market movement. A company may obtain or activate an ASN before it markets a new service publicly. It may add transit before onboarding a hosted platform. It may announce IPv6 before it publishes customer-facing IPv6 product details. It may monitor a service before making it easy to buy online. If the analyst turns every early signal into a mature category, the map becomes noisy. If the analyst ignores early signals, the map misses emerging operators. Q-MEX sits exactly where that balance is needed.

The market significance of Q-MEX's footprint

In market terms, Q-MEX is not significant because of raw scale. Four IPv4 /24s and one IPv6 /48 are small compared with national carriers, hyperscale clouds, major hosting groups or cable operators. The significance lies in control and bundling. A smaller company with its own autonomous system can create a more integrated service stack for business customers than one that simply resells a patchwork of third-party portals. It can present the customer with managed IT, backup, telephony, e-mail security, SIEM, cloud resources and connectivity as one operational relationship.

That matters for German small and mid-sized enterprises. Many such customers do not buy infrastructure as separate categories. They want secure mail, recoverable data, working phones, accessible files, monitored systems and responsive support. The access line, firewall, backup repository, hosted server and telephony endpoint may all be part of one service relationship. A provider like Q-MEX can compete not by matching Deutsche Telekom or Vodafone on national footprint, but by reducing operational complexity for business customers.

The status page makes that bundle visible. When a maintenance window touches 3CX, Hosted Exchange, Internet connections, network routing, online backup, data centres, telephony, virtual infrastructure and website service, the reader can see the service stack as an integrated production environment. The LWLCOM 10 Gbit/s upgrade note suggests capacity planning behind that environment. Even if Q-MEX is not a public regional ISP, it is still participating in the infrastructure layer that business customers depend on.

The company's partner and product signals fit this pattern. Veeam-based backup, WatchGuard firewalls, innovaphone telephony, 3CX and hosted Exchange are not obscure experiments. They are familiar building blocks in European managed IT. Q-MEX's role is to package, operate, secure and support them. The ASN and address resources become part of the reliability proposition. The customer may never ask about AS211664, but the provider's ability to route, monitor and upgrade connectivity can shape service quality.

For investors, competitors and buyers, the main unanswered question is product mix. If most revenue comes from support and integration, Q-MEX is a managed IT provider with network resources. If a meaningful share comes from Q-LINE access or managed connectivity, it is a business connectivity provider with MSP depth. If hosted infrastructure and backup dominate, it is a small cloud and continuity operator with its own network edge. Public evidence points to all three surfaces but does not quantify them.

What should not be inferred too quickly

The first overreach would be to treat Q-MEX's autonomous system as a direct proxy for market share. AS211664 tells us that Q-MEX can originate routes and that those routes are visible. It does not tell us how many customers sit behind those prefixes, whether the customers are access customers, hosted-service customers or internal platforms, or how much revenue the network layer generates. A compact routing table can support a valuable niche business, and a valuable niche business can still be small in national telecom terms.

The second overreach would be to treat every monitored service as a separate product sold to the open market. A status page reflects how an operator thinks about service availability. It can expose product lines, but it can also expose internal components, shared dependencies and bundled capabilities. Q-MEX's status page is strong evidence because it names Internet connections, routing, hosted infrastructure and data-centre labels. It is not a price list. It should be used to understand operating scope, not to invent a catalogue beyond the named services.

The third overreach would be to assume that the public website tells the whole story. Small German business providers often sell through direct relationships, quotations, referrals and partner channels rather than through exhaustive product pages. Q-MEX may have more detailed connectivity offers in proposals, contracts or customer discussions than it publishes online. That possibility raises the upside case, but it cannot replace public evidence in a published classification. The article can identify the signals that point toward connectivity without turning them into settled fact.

The fourth overreach would be to separate the network layer from the managed-services layer too cleanly. In practice, the same provider may use one routing footprint to support hosted Exchange, mail filtering, backup repositories, SIEM collectors, VPN endpoints, telephony gateways, customer firewalls and business access lines. The economic unit may be the managed relationship, not the individual prefix. That is why the institutional category remains useful: it allows the analysis to recognise Q-MEX as an infrastructure-relevant institution without forcing a consumer or regional carrier model onto a company whose public posture is broader and more consultative.

The fifth overreach would be to call the ASN dormant because the company is not widely visible in mainstream telecom coverage. Dormancy is a technical and operational claim, not a brand-recognition claim. On July 9, 2026, the public routing sources showed active announcements, and the company's own status surface showed operational network services. The better phrase is "live but still under-documented as an access ISP." That phrase captures both sides of the evidence: the network is not imaginary, and the ISP label still needs stronger commercial proof.

Evidence notes

The strongest identity evidence is Q-MEX's own Impressum at https://www.q-mex.net/impressum/, which names Q-MEX Networks GmbH, managing director Markus Plischke, Delmenhorst address, phone, e-mail and VAT identifier. RIPE's organisation object at https://rest.db.ripe.net/ripe/organisation/ORG-QNG1-RIPE.json independently names Q-MEX Networks GmbH, country DE, LIR organisation type and the Walsrode HRB 206998 registration reference.

The strongest service evidence is Q-MEX's own home page at https://www.q-mex.net/, About page at https://www.q-mex.net/ueber-uns/, Cloud and Network IT page at https://www.q-mex.net/cloud-netzwerk-it/, IT outsourcing page at https://www.q-mex.net/it-outsourcing/, backup page at https://www.q-mex.net/smarte-backups/, Q-SIEM page at https://www.q-mex.net/q-siem/ and innovaphone telephony page at https://www.q-mex.net/smarte-telefonie-mit-innovaphone/. Together they support the managed IT, hosted infrastructure, backup, security, telephony and business-service reading.

The strongest operating evidence is Q-MEX's public status page at https://status.q-mex.net/ and status API at https://status.q-mex.net/api/status. The status page lists monitored services, including Internetanschluesse (Q-LINE), Netzwerk und Routing, Virtuelle Infrastruktur (Q-IaaS), Online Backup, Hosted Exchange, Telefonie, RZ BRE01 and RZ DEL01. It also records the July 4, 2026 maintenance window for an outside-bandwidth upgrade, including a stated expansion of the LWLCOM connection to 10 Gbit/s.

The strongest routing evidence is RIPE's aut-num object at https://rest.db.ripe.net/ripe/aut-num/AS211664.json, RIPEstat routing status at https://stat.ripe.net/data/routing-status/data.json?resource=AS211664, RIPEstat announced prefixes at https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS211664, and PeeringDB's API entry at https://www.peeringdb.com/api/net?asn=211664. These sources support AS211664 assignment, upstream policy naming LWLCOM, Cogent and COLT, current announcement visibility, prefix list, open peering-policy profile and IRR AS-SET context.

The address-resource evidence comes from RIPE allocation and route objects, including https://rest.db.ripe.net/ripe/inetnum/91.232.22.0%20-%2091.232.23.255.json, https://rest.db.ripe.net/ripe/inetnum/185.226.240.0%20-%20185.226.243.255.json, https://rest.db.ripe.net/ripe/route/91.232.22.0%2F24AS211664.json, https://rest.db.ripe.net/ripe/route/185.226.241.0%2F24AS211664.json and https://rest.db.ripe.net/ripe/route6/2a12%3A84c0%3A1%3A%3A%2F48AS211664.json. These sources show allocated IPv4 ranges and route objects originated by AS211664.

The main limit is commercial specificity. Public evidence shows Q-MEX as a live network-resource holder and a managed-service provider with Internet-access signals. It does not yet show enough access-product detail to classify the company as a regional ISP with high confidence. The best current conclusion is therefore narrower: Q-MEX is a German institutional service provider with live routing, hosted-service infrastructure and a plausible business-connectivity surface that deserves continued observation.