e& coverage problems: telling an outage from a capacity issue from your building
These three look identical on your phone and need three different fixes. Twenty minutes of testing separates them, and it decides whether your ticket gets action or gets closed 'no fault found'.
Run the three-line test
First, the pattern in time: an outage is sudden and constant (nothing works, was fine yesterday); a capacity problem is a shape (fine at 4am, useless at 9pm, works on weekends); a building problem is a place (works in the car park, dies in the same room every day).
Second, the pattern across lines: compare an e& line against another e& line at the same spot, then against a different operator at the same spot. If only one line fails, the SIM or plan is the suspect. If every operator fails in one room, the building is the suspect - film, concrete, distance from the street cabinet. If every e& line in the neighbourhood fails, it is the network.
What to do for each cause
Outage: report once with the address and the start time, ask for a fault reference, and ask specifically whether the site is under maintenance or has a traffic-collision flag. A reference is what allows an escalation and, on a business account, a service-credit conversation.
Capacity: the fix at your end is offloading - Wi-Fi calling on, and if you are on a lower tier, check whether the site is congested on 4G while 5G is free (and vice versa); forcing the other radio for the busy hours is a real workaround.
Building: no plan change fixes physics. Options are Wi-Fi calling (cheapest, immediate), a signal repeater that is legal and operator-approved (not a grey-market booster, which will bring the wrong kind of attention), or moving the access point - on fibre, the cabinet, not the phone - closer to the living space.
Before you accept 'no fault found'
Give them something measurable: the times it fails, the number of affected lines, a screenshot of the signal bars with a timestamp, and a speed test result at the same moment. A 'no fault found' reply against a fault log with dates is an escalation, not an answer.
Ask for a site check rather than a line check when the whole address is affected. Individual line tests each pass - the fault is not on the line, it is on the cell or the wiring to the building.
What to use, exactly
| Task | How |
|---|---|
| Report a network fault | the app's fault-reporting flow or the care line, with the address and start time |
| Check coverage at an address | the operator's coverage checker, using the building rather than the area name |
| Force the other radio | phone settings > mobile network > preferred network type |
Keep these open next to each other
Say it in one message
Tell us the number type (prepaid, postpaid, business), what the device shows and what you already tried. If it is ours to chase, we will draft the request for you.
Send it on WhatsAppWhere to check it yourself
- The operator's own plan and support pages - the text your order form was written from
- The regulator's complaint portal - what to file, in what order, with which evidence
These pages belong to the operator and the regulator - open them side by side with your own bill or app before acting on anything here.
Verify this yourself in two minutes
- Prices and inclusions: the operator's own plan page for your emirate, then the same figure on the order form you signed.
- Your line state: the My du app - Account > Services shows suspension, bar, data cap and contract end.
- Faults in your area: My du app > Support > Outage status, or 155 from a du mobile (free).
- Anything regulatory (billing disputes, escalation): TDRA - your complaint must cite the ticket number du gave you, dated.
Confirm the current fee and the exact menu path in the operator app before you act on anything here.
If a number on this page and a number in your app disagree, the app wins - and we would like to know: WhatsApp us the screenshot and we correct the page.