Mada Al-Arab General Services sells hosting continuity before raw speed

Summary

• Mada Al-Arab General Services Company is not only a retail internet brand. Its public company pages, RIPE registration, AS51407 routing record and PeeringDB profile support a reading of Mada as a Palestinian connectivity, hosting, data-center and recovery provider whose paid unit is continuity for accounts that would find migration disruptive.
• The public evidence is strongest on identity, network resources, business service categories, peering, international connectivity claims, and support/complaint machinery. It is weakest on private economics: enterprise revenue share, churn, account-level uptime, colocation utilization, customer concentration, gross margin and renewal discipline remain unverified.
• The investment question is whether Mada can convert local support, fiber reach, route control, hosting tools, backup geography and buyer inertia into durable accounts against hyperscale cloud, other local hosts, reseller platforms, in-house servers, website builders and delayed migration.
• The risk case is that continuity has to be proven in outages, migrations, abuse events and billing disputes. Public routing and service pages show capacity to sell that promise; they do not prove how often customers renew after a bad month.

The renewal is the economic event

The most useful way to value Mada Al-Arab General Services Company is not to start with an advertised speed. Start with a buyer on a renewal date. A clinic, school, small bank supplier, retailer, municipal contractor, professional-services office or online merchant has a domain, email accounts, a hosted site, a backup routine, several branch links and an internet line that staff now treat as ordinary. The buyer can move to a hyperscale cloud, another Palestinian host, a reseller platform, an in-house server, a website builder or simply delay a migration for another year. Each option has a sticker price. The real price is the lost weekend, the risk of a broken mailbox, the forgotten DNS record, the support call at the wrong hour, the backup that fails during transfer and the employee who knows the old provider's control panel better than the new one.

That is the account Mada wants to keep. The company title in the local intelligence directory is "Mada Al-Arab General Services Company", and the directory identifies it as a Palestinian company connected with ASN and IP network resources in Palestine (https://btw.media/en/directory/mada-al-arab-general-services-company-ps). The directory fact alone is not enough to explain its economics. The economics emerge when that identity is matched with the company's own product pages and public routing records. Mada presents itself as a telecommunications and internet operator founded in 2010, with fiber services for individuals and businesses, international gateway references in London and Frankfurt, a 2019 strategic partnership with the Palestine Investment Fund, Bank of Palestine as a major shareholder, a 2022 fiber-network licence agreement, more than 300 professionals and more than 1,400 sales and payment points (https://mada.ps/ar/about-mada/). These claims are company-authored, so they should not be read as audited proof of profit. They are still important because they define the commercial story Mada is asking customers to buy: local infrastructure, local reach, financial backing, and support density.

The paid unit therefore needs to be explicit by the third paragraph: Mada sells a hosting, cloud or data-service continuity account. It may invoice connectivity, hosting, colocation, domain registration, branch linking or disaster recovery separately, but the buyer is often paying for the package to remain known, reachable and repairable. The speed of a fiber plan matters, but speed is not the whole value proposition when a business account has already embedded email, hosting, backup, internal links and support habits around one provider. A provider that owns customer history, local access, technical contacts and live network resources can hold a customer even when another provider can quote a faster or cheaper line.

That thesis has to be tested against public evidence. Mada's business-services page lists business internet, data connectivity, website hosting, SMS packages, data center, audio and video broadcasting, internal networks and disaster recovery (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/). The list is a product menu, not a sales ledger. Still, the categories fit a continuity account. Business internet brings the account online. Data connectivity links sites. Hosting and domain registration keep the public presence live. Data center and disaster recovery keep data available. Internal networks and broadcasting add specialized services that can deepen dependence. The buyer who uses only one product can churn more easily than the buyer who has three or four operational threads tied to the same provider.

Mada's public material does not prove that its customers stay because they love the service. It proves that the company sells the kinds of services in which renewal inertia can become valuable. A basic website can be rebuilt elsewhere. A website plus company email plus control-panel habits plus backup expectations plus branch connectivity plus a known technical contact is harder to move. That friction is not automatically good for customers; it can be a source of lock-in. It is, however, the economic surface that matters for judging the company.

What public evidence actually proves

The public record proves a real network operator with a live AS and business-service catalogue. The RIPE organisation object for ORG-MAL7-RIPE lists "Mada Al-Arab General Services Company", country PS, registration number 562480616, organisation type LIR, a Jerusalem postal address, contact details, admin and abuse references, a creation date in August 2010 and a last-modified date in May 2026 (https://rest.db.ripe.net/ripe/organisation/ORG-MAL7-RIPE). The LIR designation is important because it shows a direct registry role in number-resource administration rather than only a reseller identity. It does not show revenue, customer count or network quality.

RIPE inverse records tied to ORG-MAL7-RIPE show multiple IPv4 allocations and assignments under Mada-related netnames, including ranges beginning 176.65.16.0, 176.67.56.0, 176.67.96.0, 178.130.144.0, 185.17.232.0, 185.7.120.0, 188.227.232.0, 195.35.85.0, 31.13.160.0, 31.220.148.0, 31.25.72.0, 37.60.144.0, 37.76.192.0, 46.244.64.0 and 46.28.136.0 (https://rest.db.ripe.net/search.json?inverse-attribute=org&query-string=ORG-MAL7-RIPE). Those ranges should be treated as network evidence, not as separate company entities. They show resource control and routing surface. They do not tell us how much traffic is retail broadband, enterprise internet, hosted workloads, wholesale service or unused address space.

RIPEstat gives a clean origin check. For 176.65.16.0/20, RIPEstat returns AS51407 with holder "Mada-AS Mada Al-Arab General Services Company" (https://stat.ripe.net/data/prefix-overview/data.json?resource=176.65.16.0/20). RIPEstat's AS overview for AS51407 lists the AS as announced and assigned by RIPE NCC (https://stat.ripe.net/data/as-overview/data.json?resource=AS51407). Hurricane Electric's BGP Toolkit independently lists AS51407 as "Mada Al-Arab General Services Company", with a company website, Palestine as country of origin, two internet exchanges, 279 originated prefixes, 277 originated IPv4 prefixes, two originated IPv6 prefixes, zero RPKI-originated invalids, 20 observed IPv4 peers, four observed IPv6 peers and 110,080 originated IPv4 addresses (https://bgp.he.net/AS51407). These are strong signals that Mada is not merely a paper hosting reseller.

PeeringDB adds an industry self-profile. Its AS51407 page lists "Mada Al-Arab", also known as "Mada Palestine", with website http://www.mada.ps, route set AS-MADASET, network type Cable/DSL/ISP, 300 IPv4 prefixes, seven IPv6 prefixes, traffic level of 100-200Gbps, mostly inbound traffic ratio, Middle East scope, selective peering policy, and public contacts for technical, sales and abuse functions (https://www.peeringdb.com/net/7590). It also lists operational 10G connections at DE-CIX Frankfurt and the Palestine Internet Exchange Point, plus an interconnection facility at MTIT Building 01 in Ramallah. PeeringDB is self-maintained, and update dates vary by field, so it is not an audit. But it is exactly the sort of public industry profile that helps explain a continuity proposition: there is a network, there are exchange points, there are contacts, and there is an AS that customers and peers can identify.

The company's own service pages fit this infrastructure. Its business-internet page says it offers high-speed internet for corporate and business customers through fiber networks, with symmetric or asymmetric options, FTTS for small and medium businesses and METRO for larger companies (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D9%86%D8%AA%D8%B1%D9%86%D8%AA-%D8%A7%D8%B9%D9%85%D8%A7%D9%84/). Its data-connectivity page says it links company and institutional branches inside or outside Palestine, with high availability, high speeds, advanced fiber and international lines, SDH or Ethernet service, protected lines, specialized 24-hour technical support and coverage across Palestinian cities in the West Bank, Gaza and Jerusalem, plus international interconnection with global exchange points in London, Frankfurt and Jordan (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D9%84%D8%B1%D8%A8%D8%B7-%D8%A7%D9%84%D8%A8%D9%8A%D9%86%D9%8A-%D8%A7%D9%84%D8%AF%D9%88%D9%84%D9%8A/). Again, this is not proof of delivered uptime. It is proof of the promise being sold.

The most useful discipline is to separate fact from commercial inference. Public evidence proves that Mada has a direct registry identity, live public routing, a business-services portfolio and industry interconnection references. It does not prove how often its business internet meets promised availability, how quickly staff resolve incidents, how many customers host production workloads, how much revenue comes from colocation or how much gross margin sits inside the hosting account. A serious view of Mada must therefore be conditional: public evidence supports the continuity thesis, while private operating data would decide whether that thesis is profitable.

The product ladder is built for dependence

Mada's business product ladder has a clear dependence logic. The first layer is access: a business line, often fiber, that connects an office or branch to the network. The second layer is inter-site connectivity: branch links, SDH or Ethernet options and international data connectivity. The third layer is public presence: domain registration, website hosting, company email and control-panel administration. The fourth layer is operational custody: colocation, data storage, backup centers and disaster recovery. Each layer has a different price structure, but the combination changes the buyer's behavior. A buyer that uses only broadband can compare speed and price. A buyer that uses broadband plus hosting plus backup has to price operational disruption.

The hosting page makes this plain. Mada describes domain registration, website hosting, storage space for a website and company email, and account management through a control panel. It specifically mentions email-account setup, new folders, file deletion and backup creation as tasks managed through that panel (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D8%B3%D8%AA%D8%B6%D8%A7%D9%81%D8%A9-%D8%A7%D9%84%D9%85%D9%88%D8%A7%D9%82%D8%B9/). These are small tasks, but they are the tasks that generate support memory. A local provider that knows which office manager calls about mailboxes, which technician changed DNS last year and which backup routine was set up during a previous incident can sell convenience that a cheaper offshore host may not match.

The data-center page widens the account from website hosting to business-data custody. Mada says it provides storage spaces within its data centers to allow customers to store business data in a suitable and secure environment, and says the service provides high levels of data protection within backup storage centers inside Palestine and abroad (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/data-center/). The disaster-recovery page similarly describes storage spaces in data centers in Palestine and abroad so subscribers can store business data and ensure protection and availability when sudden risk or setback occurs (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D9%84%D8%AA%D8%B9%D8%A7%D9%81%D9%8A-%D9%85%D9%86-%D8%A7%D9%84%D9%83%D9%88%D8%A7%D8%B1%D8%AB/). The public pages do not state recovery-time objectives, recovery-point objectives, certifications, power architecture, cooling design or test frequency. But they do show the language of availability, protection and geographic redundancy.

That language matters because it is not the language of commodity speed. A speed seller advertises more megabits. A continuity seller advertises branch reach, backup, support and data protection. Mada's public pages contain both. The consumer FTTH page emphasizes high download and upload speeds, stable advanced networks, no landline subscription requirement and suitability for heavy uses such as high-definition video and online gaming (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA%D9%86%D8%A7/%D8%A7%D9%84%D9%81%D8%A7%D9%8A%D8%A8%D8%B1-%D8%A7%D9%84%D9%85%D9%86%D8%B2%D9%84%D9%8A/). The corporate pages talk more about service form, support and resilience. The gap between those pages is the business model: retail volume helps build access density, but business accounts may carry more defensible revenue if they attach services around the line.

The ladder also helps explain why a local provider can survive alongside global cloud. Hyperscale cloud is often technically superior for elastic compute, managed databases and global redundancy. But a Palestinian customer does not always buy only compute. The buyer may need a local phone call, Arabic support, physical installation, a branch link, a site visit, a complaint channel, a familiar bill, and confidence that the provider understands local access constraints. A global cloud account solves some problems and creates others: payment setup, compliance comfort, migration skills, latency path, backup design and dependence on another layer of external platforms. Mada's opportunity sits in the messy middle between broadband and full cloud transformation.

The weakness of that opportunity is that public information does not show how much of the ladder customers actually climb. The product list could describe a broad catalogue with limited adoption, or it could describe a deeply bundled business account base. Without customer counts, segment revenue, renewal rates or service-level performance, we cannot tell. The public evidence supports the existence of the ladder. It does not price the ladder.

Pricing starts with friction, not only tariff sheets

Mada's public consumer pricing and contract material offers a useful anchor even though it is not enterprise pricing. A World Cup FTTH campaign page advertises 600 Mbps for 130 shekels including VAT, with a condition that current and new FTTH subscribers commit for at least 24 months and sign the service contract (https://mada.ps/ar/%D8%AD%D9%85%D9%84%D8%A7%D8%AA/400m/). The main FTTH page says prices are in shekels including VAT, and that if a subscriber ends service before the 12-month commitment period, the subscriber must pay the full 400 shekel installation fee and the full 400 shekel terminal-device price (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA%D9%86%D8%A7/%D8%A7%D9%84%D9%81%D8%A7%D9%8A%D8%A8%D8%B1-%D8%A7%D9%84%D9%85%D9%86%D8%B2%D9%84%D9%8A/). Those numbers do not tell us Mada's margin. They do reveal how the retail market prices commitment, installation and equipment recovery.

Business pricing is not published in the same simple way. Corporate pages direct customers to corporate@mada.ps or a form, which implies custom quotation or at least assisted selling. For business internet, the distinction between FTTS and METRO already suggests that the price is tied to service form and customer size rather than only headline speed. For hosting, the company says it offers different capacities suited to customer needs. For data center and recovery services, the page gives a contact rather than a package grid. That is normal for services in which the provider needs to know space, traffic, redundancy, support hours, backup volume, branch count and risk tolerance before quoting.

The renewal price is therefore made of four parts. The first is the explicit monthly bill. The second is the migration cost: domain changes, mail migration, backup transfer, staff time, downtime risk and testing. The third is support replacement: who understands the existing setup, who answers after hours, who owns previous case history, who can visit or escalate locally. The fourth is risk adjustment: what happens if a geopolitical or infrastructure shock hits during the migration or just after the buyer leaves a known provider. A low-cost substitute can win only if the buyer believes those hidden costs are small.

That is why the buyer's substitute set is broad but uneven. A hyperscale cloud can beat a local host on redundancy options and service menu, but it requires technical skill, payment confidence and operational redesign. Another local host can beat Mada on price or relationship but may lack the same routing scale, support footprint or product breadth. A reseller platform can be cheap and simple but may be less accountable when abuse handling, DNS, mail or local connectivity breaks. An in-house server can give control but shifts power, cooling, security and backup responsibility to the buyer. A website builder can solve brochure-site needs but not branch connectivity, business internet or data recovery. Delayed migration costs nothing today but preserves dependence and can create a larger failure later.

Mada's public support material reinforces the friction story. The company hosts a cPanel two-factor authentication guide explaining that two-step verification protects the customer's cPanel account and website data from unauthorized access (https://mada.ps/ar/cpanel/). This is a small support article, but it points to the operational texture of the hosting account: customers are not only buying storage; they are managing accounts, credentials and security practices. A buyer that has already trained staff on a provider's control panel may not migrate unless the new provider is clearly better.

The strongest pricing evidence that remains missing is renewal behavior. If Mada can show high renewal rates among business internet, hosting and recovery customers, then the continuity thesis becomes more than plausible. If churn is high after promotional periods, or if customers use Mada only for access while hosting workloads elsewhere, the thesis weakens. If customers leave only when a major outage or billing dispute occurs, then uptime and support response become the core valuation variables. Public pages can define the contract surface; they cannot reveal the renewal curve.

Cost base: fiber, routes, support and stored responsibility

The continuity account also creates costs that pure speed analysis can miss. Access requires network build, installation labor, customer equipment, maintenance, power backup, field operations and support. Business connectivity adds provisioning, monitoring, route engineering, contract management and escalation. Hosting adds servers, storage, software licences, security hardening, mail reputation, backups and abuse handling. Data center and recovery services add power, cooling, physical security, space, redundancy, backup geography and testing. The more Mada sells continuity, the more it has to fund the boring systems that make continuity true.

Public sources show some of these costs indirectly. Mada's about page says the company owns and operates fiber networks covering Palestinian governorates in the West Bank and Gaza Strip, connects globally through interconnection lines with telecommunications networks worldwide, and has presence in London and Frankfurt (https://mada.ps/ar/about-mada/). Its data-connectivity page references international lines with exchange points in London, Frankfurt and Jordan, as well as 24-hour specialized support (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D9%84%D8%B1%D8%A8%D8%B7-%D8%A7%D9%84%D8%A8%D9%8A%D9%86%D9%8A-%D8%A7%D9%84%D8%AF%D9%88%D9%84%D9%8A/). PeeringDB lists 10G operational exchange connections at DE-CIX Frankfurt and PSIX, and a Ramallah facility (https://www.peeringdb.com/net/7590). RIPEstat and Hurricane Electric show a live AS with large visible IPv4 surface (https://stat.ripe.net/data/as-overview/data.json?resource=AS51407 and https://bgp.he.net/AS51407). These pieces point to a cost base beyond a simple reseller website.

The cost question is whether those fixed and semi-fixed costs are covered by enough durable accounts. Fiber and exchange presence create operating leverage when they serve many customers, but they can pressure margins when utilization is low. Hosting and recovery services can add higher-margin recurring revenue if customers value them, but they can also add support load and incident exposure. A backup promise is cheap to write on a product page and expensive to prove during a failure. If a provider sells recovery, it must pay for the systems, staff and discipline to make recovery credible.

Abuse handling is part of the cost base. Mada's fair-use policy warns against illegal resale or distribution of service, commercial VoIP without licence, hacking, illegal activity and unlicensed internet cafes; it says historical company records indicate less than 1 percent of subscribers engage in such listed misuse (https://mada.ps/ar/%D8%B3%D9%8A%D8%A7%D8%B3%D8%A9-%D8%A7%D9%84%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85-%D8%A7%D9%84%D8%B9%D8%A7%D8%AF%D9%84/). The less-than-1-percent figure is company-stated and should not be treated as independently verified. The policy is still economically relevant. Misuse can degrade service for other customers, damage mail or network reputation, trigger complaints, consume support time and create regulatory exposure. For a provider selling continuity, abuse control is not a side matter; it protects the service experience of paying accounts.

Support labor is another cost that can become an asset. Mada says it employs more than 300 qualified professionals and has more than 1,400 sales and payment points (https://mada.ps/ar/about-mada/). The complaints page separates complaint categories into commercial, customer-care and technical management, and allows customers to complain by form, phone, office visit, sales/payment-point visit or email (https://mada.ps/ar/%D8%A7%D9%84%D8%B4%D9%83%D8%A7%D9%88%D9%8A/). The privacy page says customer information may be used to follow subscriptions, requests and transactions; communicate on technical and financial matters; verify authorized contacts; notify customers about maintenance, emergency interruptions and related service impacts; and evaluate and develop products and services (https://mada.ps/ar/privacy_policy/). These are not customer-satisfaction proofs. They are evidence that the company has a support and account-management surface. In a continuity business, that surface is part of the product.

The private cost facts that would change the assessment are straightforward. What is Mada's business internet gross margin after access, upstream, support and installation recovery? How much of hosting revenue is true hosted infrastructure rather than low-margin domain resale? What share of data-center and recovery capacity is utilized? How many serious incidents require manual support each month? How much is spent on international connectivity, DDoS mitigation, backup storage and field maintenance? Public evidence cannot answer these questions. It can only show why they matter.

Supplier and upstream dependence

Mada's public routing profile suggests a network that is not isolated. RIPEstat's neighbour view for AS51407 shows observed left-side neighbours including AS1299 Arelion Sweden AB, AS286 KPN/GTT, AS3257 GTT Communications, AS33891 Core-Backbone, AS3491 PCCW Global, AS35280 F5 Networks, AS59796 StormWall and AS8551 Bezeq International (https://stat.ripe.net/data/asn-neighbours/data.json?resource=AS51407). Hurricane Electric lists observed IPv4 peers including GTT, Arelion, StormWall, PCCW Global, F5 Networks and Core-Backbone (https://bgp.he.net/AS51407). These are route observations, not contracts. They should not be overread as a definitive supplier list. They still matter because they show the public path environment around AS51407.

The upstream map changes the economics in two ways. First, multi-neighbour visibility can support resilience if routes are engineered and capacity is sufficient. A hosting buyer does not care about AS-path theory on a normal day, but cares deeply when one carrier path degrades. Second, international dependence can be a cost and risk. Access to London, Frankfurt, Jordan and regional exchange points may improve reachability, but it also means Mada's service depends on cross-border circuits, carrier relationships, routing policy and physical infrastructure that are not fully under its control.

PeeringDB's exchange data is useful here. AS51407 is listed at DE-CIX Frankfurt and the Palestine Internet Exchange Point, each at 10G and operational, with a Ramallah facility at MTIT Building 01 (https://www.peeringdb.com/net/7590). DE-CIX Frankfurt presence can improve access to international peers and transit ecosystems. PSIX presence can improve local exchange and reduce unnecessary tromboning when counterparties also peer locally. A local hosting or business internet account benefits when domestic or regional traffic can stay efficient, and when international traffic can exit through stable interconnection. But the public listing does not show port utilization, route policy quality, congestion history or failover success.

The company site also claims global connectivity through international gateways in London and Frankfurt (https://mada.ps/ar/about-mada/) and data-connectivity international lines with global exchange points in London, Frankfurt and Jordan (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA-%D8%A7%D9%84%D8%B4%D8%B1%D9%83%D8%A7%D8%AA/%D8%A7%D9%84%D8%B1%D8%A8%D8%B7-%D8%A7%D9%84%D8%A8%D9%8A%D9%86%D9%8A-%D8%A7%D9%84%D8%AF%D9%88%D9%84%D9%8A/). The gap between the company claim and the public BGP view is not necessarily a contradiction; companies describe commercial gateways and BGP observers see public paths from selected vantage points. The prudent reading is that Mada has multiple public and claimed international connectivity channels, but the durability of those channels must be judged by operational performance, not by the existence of records alone.

Supplier dependence also includes technology and security services. Hurricane Electric lists F5 Networks and StormWall among observed peers or neighbours (https://bgp.he.net/AS51407). The public record does not tell us whether these relationships reflect security, transit, customer, peering or other functions. It would be tempting but wrong to infer a complete DDoS-protection architecture from those names. The correct conclusion is narrower: public BGP evidence shows AS51407 in a broader routing environment that includes security and backbone networks. The actual risk transfer depends on private service terms.

For the customer, the supplier question becomes simple: if one path fails, who notices, who reroutes, who answers and how much capacity remains? That is a support and engineering question, not just a procurement question. Mada's continuity account is credible only if the route map, support desk and customer communication system behave together during stress.

Customer dependence and market shape

Mada operates in a Palestinian telecom market where incumbents and mobile operators also shape customer expectations. Paltel Group's official site describes the Palestinian Telecommunications/Jawwal group as a leading telecommunications company in Palestine, established in 1995 as a public shareholding company that provides fixed, mobile and internet services and is a major private-sector employer (https://www.paltelgroup.ps/). Ooredoo Palestine's homepage shows consumer, business, device, roaming, service, eSIM and business-solution offers (https://www.ooredoo.ps/). These competitors do not map one-to-one against Mada's hosting and data-service proposition, but they shape the substitute set. A customer compares Mada not only with another host, but with broader communications providers, mobile bundles and established fixed-line options.

The local buyer base is also heterogeneous. A household buyer may switch for price, speed, installation convenience or promotion. A small business may care about price but be more sensitive to downtime, email continuity and support. A larger business may care about symmetric service, branch connectivity, route quality, data custody, backup geography and escalation. Public Mada pages address all three layers: consumer FTTH, business internet and business continuity services. The economic question is which layer contributes the most durable revenue.

Mada's availability-check page asks for location, package, name, phone, email and notes (https://mada.ps/ar/%D9%81%D8%AD%D8%B5-%D8%A7%D9%84%D8%A7%D9%85%D9%83%D8%A7%D9%86%D9%8A%D8%A9/). This looks ordinary, but it reveals how physical coverage remains part of the product. Cloud companies can sell globally with a login. Access providers have to know whether fiber can be installed at a specific location. That coverage qualification process can slow sales, but it also creates relationship data and local context. If Mada can convert a coverage inquiry into a multi-service account, the initial access sale becomes a gateway to hosting and continuity revenue.

The customer-dependence story should not be romanticized. Buyers may also depend on Mada because migration is annoying, not because the service is excellent. That creates risk. If a competitor offers assisted migration, if a website builder makes email transfer easier, if a cloud partner packages local support, or if a bad support incident breaks trust, the same customers can churn. The continuity account is sticky only while the perceived risk of leaving is greater than the perceived risk of staying.

Market dependence is also shaped by purchasing power and contract norms. The public consumer campaign at 130 shekels including VAT for 600 Mbps FTTH under a 24-month commitment shows aggressive speed-price messaging at the retail layer (https://mada.ps/ar/%D8%AD%D9%85%D9%84%D8%A7%D8%AA/400m/). If consumers are trained to buy speed cheaply, business services must justify a different price language. Mada's corporate pages use that different language: availability, branch links, data protection, backup and technical support. The company needs enough customers who believe those words have economic value.

The future facts that matter are customer mix and account attachment. If most Mada revenue comes from residential access, then hosting continuity is a smaller thesis. If a meaningful share comes from business internet plus hosting plus backup, the company has more defensible recurring revenue. If data-center and recovery services are lightly used, they may be marketing extensions. If they are embedded in banks, clinics, professional services, universities, public bodies or merchants, they could be strategic. Public pages cannot resolve this; interviews, contracts, audited segment data or credible customer case material would.

Competition and substitution

The first substitute is hyperscale cloud. For a buyer with technical staff and payment comfort, cloud offers elastic compute, managed storage, global regions, security tooling and mature backup options. It can also make local hosting look underpowered. Yet cloud is not a complete substitute for local access, branch connectivity, physical installation, phone support or local billing. A Palestinian business that wants one provider to handle internet access, branch link, hosting and backup may still prefer a local operator. The cloud is strongest when the buyer can redesign the workload; Mada is stronger when the buyer wants continuity without redesign.

The second substitute is another local host or ISP. This is the most direct threat. A local rival can offer the same language of support and proximity. If the rival has better uptime, clearer pricing, stronger migration help or more responsive staff, Mada's account friction weakens. Mada's defense is public network scale, routing visibility, business service breadth and existing customer habits. The defense is not unbeatable. It has to be renewed with each outage response and support interaction.

The third substitute is a reseller platform. Reseller hosting can be cheap, familiar and easy to buy. It can work well for brochure sites and simple email. It becomes less attractive when the buyer needs local data custody, branch connectivity, a local network incident response, Arabic support, or a provider that can explain why connectivity and hosting are failing together. Mada's advantage is integration. The reseller's advantage is simplicity and price.

The fourth substitute is an in-house server or private equipment hosted by the buyer. This option appeals to customers that want control or distrust external custody. It also moves power, cooling, physical security, patching, backup, monitoring and incident response onto the buyer. For many small and medium organizations, that is false economy. Mada's data-center and disaster-recovery pages are aimed at the cost of that false economy: a customer may own the workload, but not want to own the environment that keeps it available.

The fifth substitute is a website builder or managed software platform. For simple public sites, this can be a serious alternative. It reduces the need to think about cPanel, server space, patches and backups. But website builders do not replace branch connectivity, business internet, data-center custody or recovery planning. Mada should lose the simplest websites to self-service platforms over time unless it bundles local support or adjacent connectivity. It should be more defensible where the website is part of a broader operational account.

The sixth substitute is delayed migration. This is often the strongest competitor in continuity services. The buyer knows the current setup is imperfect but delays change because moving is risky. That helps the incumbent in the short term. It can hurt in the long term if dissatisfaction accumulates. A provider that relies too heavily on inertia without improving service eventually creates a pool of customers waiting for a migration trigger. A provider that uses inertia to deepen support, simplify backups and improve communication can convert delay into durable trust.

Mada's visible business-service catalogue gives it a plausible answer to each substitute. It can say it is local, networked, reachable, able to support access and hosting together, and able to provide backup geography. The public evidence does not show whether customers believe it. That belief is won in renewals, not marketing pages.

Regulation, conflict and operational risk

The Palestinian connectivity market carries risks that are not normal in a stable infrastructure market. The most severe recent public context is Gaza's repeated communications disruption during the war. AP reported in October 2023 that internet and phone service gradually returned after vanishing for most of Gaza amid heavy bombardment (https://apnews.com/article/gaza-israel-war-hamas-blackout-internet-phone-abd024625526f6d808c1583afd58e2e7). AP reported further telecom-contact loss in November 2023 (https://apnews.com/article/israel-hamas-war-news-11-05-2023-eb1dfa6afe40ba267024c7d819e17194). Wired also reported on the severe destruction of Gaza's internet connectivity and the dependence of communications on vulnerable infrastructure during the war (https://www.wired.com/story/gaza-internet-blackout-israel). These reports are not Mada-specific outage evidence. They are market-risk context: in Palestine, continuity is not an abstract selling point.

That context cuts both ways. It increases the value of providers that can maintain service, communicate with customers, use backup routes and recover data. It also raises the cost and difficulty of doing so. If infrastructure is damaged, power is constrained, fuel is unavailable, routes are interrupted or staff cannot safely reach facilities, even the best provider may fail. A continuity seller in this environment must be judged with realism. The promise is not perfect uptime under every condition. The promise is better preparation, better response and clearer accountability than the substitute.

Regulatory dependence also matters. Mada's own about page says that in 2022 it signed an agreement with the Palestinian Ministry of Communications and Information Technology granting it a licence to build and operate fiber optic networks in Palestine, excluding landline telephone services (https://mada.ps/ar/about-mada/). This company-stated licence claim matters because fiber-network rights are a foundation for access and business connectivity. It also shows that Mada's scope has boundaries. The company is not simply free to provide every telecom service. Its offering exists inside a regulated market with licences, frequency and infrastructure constraints.

International connectivity creates geopolitical risk. Mada's public pages refer to international gateways and interconnection in London, Frankfurt and Jordan. PeeringDB lists DE-CIX Frankfurt and PSIX. Public BGP views show international carriers and observed peers. That diversity can help, but geography and politics still shape physical paths. A customer buying disaster recovery or branch connectivity should ask where traffic exits, where backups reside, what happens if one route is impaired, and how Mada communicates during regional disruption.

Operational risk is not limited to war. Hosting providers face disk failures, mail blacklisting, DDoS events, credential compromise, billing errors, failed backups, control-panel vulnerabilities and customer misuse. Mada's fair-use policy and cPanel security page indicate that the company is aware of misuse and account-security issues (https://mada.ps/ar/%D8%B3%D9%8A%D8%A7%D8%B3%D8%A9-%D8%A7%D9%84%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85-%D8%A7%D9%84%D8%B9%D8%A7%D8%AF%D9%84/ and https://mada.ps/ar/cpanel/). Awareness is not performance. The question is whether these controls reduce incidents enough to preserve trust.

Complaints are also part of operational risk. Mada's complaints page says customers can file complaints through a form, phone contact, visits to offices or sales/payment points, and email, including an option to send a complaint without disclosing details through info@mada.ps (https://mada.ps/ar/%D8%A7%D9%84%D8%B4%D9%83%D8%A7%D9%88%D9%8A/). A complaint channel does not prove good service. It does prove the company has a formal surface where commercial, customer-care and technical issues can be routed. For continuity accounts, complaint routing is important because a business customer may forgive a failure that is acknowledged and fixed more readily than a failure that disappears into silence.

The risk case against Mada is therefore not that public evidence is false. The risk case is that public evidence is incomplete. A company can have a live AS, exchange presence, fiber claims, hosting pages and support contacts while still delivering uneven service, slow repairs or weak recovery. The public record supports a due-diligence case. It does not close the case.

Unofficial market signals are thin

Public unofficial signals for Mada are limited. Searchable review material is not strong enough to use as representative evidence. The company has social links on its site and public-facing support, complaint, campaign and availability forms, but those do not reveal satisfaction, churn or service quality. It would be irresponsible to convert scattered comments, advertisements or forum impressions into firm conclusions about performance.

There are still market signals worth noting. First, the 600 Mbps campaign at 130 shekels including VAT and a 24-month commitment suggests a retail market where speed-price promotions are used to acquire or retain households (https://mada.ps/ar/%D8%AD%D9%85%D9%84%D8%A7%D8%AA/400m/). Second, the FTTH early-termination equipment and installation repayment language suggests the provider actively manages installation-cost recovery (https://mada.ps/ar/%D8%AE%D8%AF%D9%85%D8%A7%D8%AA%D9%86%D8%A7/%D8%A7%D9%84%D9%81%D8%A7%D9%8A%D8%A8%D8%B1-%D8%A7%D9%84%D9%85%D9%86%D8%B2%D9%84%D9%8A/). Third, the business pages use contact-led selling rather than self-service price tables, suggesting that corporate accounts may require qualification and quotation. Fourth, the complaints page exposes the categories of friction the company expects: commercial issues, customer care and technical issues (https://mada.ps/ar/%D8%A7%D9%84%D8%B4%D9%83%D8%A7%D9%88%D9%8A/).

These signals are useful only if kept in their lane. They do not prove that customers complain more or less than at competitors. They do not prove whether Mada underprices or overprices. They do not prove support quality. They suggest where the market contest happens: promotions to win access accounts, contract terms to recover upfront cost, contact-led selling for business needs, and support channels to keep customers from leaving after friction.

The absence of a robust public review corpus is itself an analytic fact. For a thinly covered operator, public network records may be much stronger than public customer evidence. That can distort analysis. The network may look impressive while customer service is weak, or the customer service may be strong while public records reveal little about it. Mada should be judged by combining registry and routing evidence with direct customer interviews, incident histories and renewal data. Public-only research can reach a probability, not a verdict.

Unofficial signals would become more useful if they were structured. A credible sample of business customers, support-ticket resolution times, net promoter style feedback, complaint closure rates, migration reasons and renewal reasons would tell us whether continuity is truly priced. Without that, the article can only say that Mada sells into a market where continuity should matter, and that public evidence supports the infrastructure side of that claim.

What would reverse the judgement

Several private or future facts would change the assessment quickly. The first is churn. If business internet, hosting and recovery customers renew at high rates, the continuity-account thesis strengthens. If customers leave after promotions, after first outages, or whenever a cheaper local provider offers migration help, the thesis weakens. Churn by product bundle matters more than blended churn. A hosting-only account, access-only account and access-plus-recovery account are different economic animals.

The second is uptime and incident response. Public pages advertise high availability and recovery, but the decisive facts are outage frequency, mean time to repair, customer notification speed, backup test success and post-incident credits. A provider can lose years of support goodwill in one badly handled outage. Conversely, a provider can retain customers after a failure if it communicates clearly, restores service quickly and proves backups work.

The third is customer mix. If Mada's most durable accounts are institutions, banks, medical providers, education providers, merchants, software firms and professional-services businesses that depend on data continuity, the company has a stronger moat. If the customer base is mostly price-sensitive residential access, the hosting-continuity frame becomes secondary. The public site points to both consumer and corporate markets; it does not reveal the revenue split.

The fourth is margin. Hosting and recovery can be attractive if priced above support and infrastructure cost. They can be unattractive if they create many manual interventions, storage costs, security incidents and underutilized facilities. Business internet can be attractive if route capacity, support and installation are well managed. It can become weak if aggressive promotions pull down pricing faster than costs decline.

The fifth is supplier concentration. Public BGP and PeeringDB evidence shows multiple visible peers and exchange points, but private contracts determine resilience. If a large share of traffic or backup capability depends on one carrier, one facility, one foreign path or one software platform, continuity risk is higher than the public route map suggests. If Mada has robust capacity and tested failover across carriers and sites, the public map understates the strength of the service.

The sixth is regulatory and physical-access change. A broader fibre licence, new infrastructure rights, easier equipment import, improved interconnection, or safer access to facilities would improve the service case. New restrictions, route interruptions, infrastructure damage, power constraints or licence limits would weaken it. This is especially important because the market context includes repeated communications disruption in Gaza and wider geopolitical stress.

The seventh is cloud adoption by local customers. If Palestinian small and medium businesses move quickly to managed cloud platforms with local integrators, Mada's basic hosting revenue may face pressure. If buyers continue to value local support, access bundling, data residency comfort and migration avoidance, Mada can remain relevant. The right question is not whether cloud is better in theory. It is whether the buyer has the skills, budget and trust to move.

Diligence questions for the account

The practical diligence for Mada should start with account composition. How many customers buy only access, how many buy access plus hosting, how many buy access plus branch connectivity, and how many buy a true continuity bundle that includes data-center or recovery service? The same company can look like a price-exposed broadband provider or a sticky business-services provider depending on this mix. Public pages show the product ladder; only internal account data can show whether customers climb it.

The second diligence point is migration history. A provider that keeps customers because no one has offered help to move is less defensible than a provider that keeps customers after a credible renewal comparison. The useful evidence would be reasons for lost accounts, reasons for saved accounts, average migration lead time, customer objections during renewal and the number of customers that return after trying another provider. This is especially important for hosting, where the technical work of moving mailboxes, DNS, files and backups can either protect Mada or expose it if a rival makes migration easy.

The third point is incident proof. Mada's public language about high availability, backup centers and technical support should be tested against dated incident records. How quickly were customers notified? How many incidents affected hosting versus access? Were backups restored in drills or only described in sales conversations? How often did customers receive credits or contract adjustments? Did the support desk know which accounts were business critical? Continuity is not a product description. It is a repeated operating behavior under pressure.

The fourth point is route and capacity headroom. Public BGP evidence and PeeringDB records establish that AS51407 is visible and interconnected, but not whether capacity is enough when a path fails or traffic surges. A buyer would want to know committed capacity, peak utilization, protected versus best-effort paths, DDoS response flow, local exchange dependence, international route diversity and the escalation path when a peer or carrier degrades. The answer may be strong, but it has to be shown operationally.

The fifth point is support economics. Local support is valuable only if it scales. If every hosting problem requires senior engineering time, margins can disappear. If first-line staff can solve common mail, DNS, backup, billing and access problems quickly, support becomes a renewal asset. Mada's public complaint and privacy pages show channels and customer-data uses; they do not show closure time, repeat-contact rate or the cost of each resolved issue.

The sixth point is trust around data location. The company says data-center and disaster-recovery services involve facilities in Palestine and abroad. Customers buying those services need clarity on where primary data sits, where backup data sits, who can access it, what legal regime applies, how restoration is tested and how a customer exits with usable data. This is not only a compliance issue. It is a commercial issue because unclear data custody weakens the renewal argument.

The final point is whether Mada can keep the business account coherent as customers modernize. A small business may begin with fiber and hosting, then add cloud accounting, online payments, customer messaging, remote work and managed security. Mada does not need to replace every software platform. It does need to remain the provider that reduces operational burden rather than becoming the legacy line item customers keep only because nobody has moved it yet.

Bottom line

Mada Al-Arab General Services Company matters because its public evidence points to more than an access reseller. It has a RIPE LIR identity, a live AS51407 routing surface, visible prefixes, PeeringDB interconnection data, a business-service catalogue that includes hosting and recovery, and official pages that sell availability, support and data protection. Those facts support the assignment thesis: Mada sells hosting continuity before raw speed.

The evidence also forces humility. Public sources do not show audited revenue, renewal curves, churn, account-level uptime, customer concentration, gross margin, server inventory, facility specifications, backup test results or private customer reviews. The article should not pretend to know those facts. It should say that Mada's public surface is consistent with a continuity business, and that the value of that business depends on private facts that are not publicly visible.

For a customer, the practical question is whether staying with Mada costs less than moving when hidden migration risk is included. For a competitor, the question is whether it can make migration painless enough to break Mada's support memory and account inertia. For Mada, the question is whether it can turn local infrastructure, route control, support labor, backup claims and customer familiarity into proof during the moments that matter: renewal, outage, migration, abuse incident, billing dispute and recovery test.

That is why raw speed is the wrong opening metric. Speed wins attention; continuity wins the renewal. Mada's public record gives it the ingredients to sell continuity. The private record would decide whether it has earned the price.