System Status
The status of every EGPHP service, checked every five minutes
- 100.00%Last 24 hours
- 99.99%Last 7 days
- 100.00%Last 30 days
Service Status
Nginx Web Hosting
Shared hosting servers and websites
EGPNL Control Panel
Server management dashboard
VPS & Cloud Servers
Virtual private server infrastructure
Email Services
Email sending and receiving
DNS Services
Domain name resolution
Payment Gateway
Payment processing via Paymob
Uptime Statistics
Measured from our own checks every five minutes since September 26, 2026.
Recent Incidents
No service has failed two checks in a row since September 26, 2026.
How a check becomes an incident
Every figure on this page comes from one routine. This is what happens between a check and the word on the badge.
A check runs
Every five minutes each of the six services above is checked and the result is added to a stored history.
One failed check
A single failure shows as Degraded Performance. It is treated as a possible blip, not yet an outage.
Two failed checks in a row
The service shows as Major Outage and an incident appears under Recent Incidents with its start time.
The next check passes
The badge returns to Operational and the incident is closed with its start and end times.
The uptime figures follow
Uptime is the share of all checks that passed over 24 hours, 7 days and 30 days, so a resolved incident stays counted in it.
What each check asks
One question per service, asked every five minutes. A failed answer is asked again two seconds later before it counts, so one dropped packet is not an outage.
Nginx Web Hosting
Does the home page of egphp.com answer over HTTPS without an error?
EGPNL Control Panel
Does the customer sign-in page answer over HTTPS without an error?
VPS & Cloud Servers
Does the cloud provider's API answer? It is where servers are created and changed.
Email Services
Does the mail server accept a connection and greet it as a mail server should?
DNS Services
Does the domain still resolve to an address?
Payment Gateway
Does the payment gateway's API answer?
The checks run from our own server. They show whether each service answers; how fast a page reaches you depends on your network, and the speed test measures that from your connection. Run the speed test
Everything shows Operational but something is wrong?
The badges show what we measure from our side. Work down this list first; each item opens with the detail.
A website does not load
Open the address from another network, such as mobile data. If it loads there, the fault is on the first network or in the DNS cache of your device, not on the server. The browser error names the cause: a timeout points to the network path, a certificate warning to the site certificate, and a 5xx code to the site server.
Email is not arriving
Look in the spam folder and read the sender bounce message. A bounce carries a status code: codes starting with 4 are temporary and the sending server retries, codes starting with 5 are permanent refusals. Then confirm the MX records of the domain point to the mail server you expect.
A domain does not resolve
DNS answers are cached for the time to live of each record, so an edited record can take that long to be seen everywhere. Ask a public resolver directly to learn whether the record itself is right.
A payment did not complete
Do not pay twice. Check whether your bank sent a notice, then contact support with the time of the attempt and your order details.
The panel or a server is slow
Note the time and what you were doing, and try a private window to rule out browser extensions. A slowdown that begins at a specific moment is easy to match against the checks.
Need Support?
If you're experiencing issues not reflected here, our support team is ready to help.
Contact Support