ROMARG logo

Is ROMARG Down?

Cloud InfrastructureLive status, outages, and incident history

No. ROMARG is up right now.

Every monitored ROMARG system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment ROMARG breaks

ROMARG is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official ROMARG status page
How we know: the official ROMARG status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

ROMARG Status Summary

As of 19:39 UTC on 14 November 2026, ROMARG is operational. PulsAPI checked ROMARG's official status page and found 15 of 15 components operational, with no active incidents. The latest incident, "Alerta de securitate PHP (CVE-2026-109618 / CVE-2026-109619)", was on Oct 22, 2026 and lasted 49h 41m.

Cite as: PulsAPI, “ROMARG status”, checked 14 November 2026, 19:39 UTC. https://www.pulsapi.com/services/romarg

ROMARG Component Status

The main ROMARG systems on this page. All 15 are operational right now.

15operational
Domain Registrar » Eurid
Operational
Domain Registrar » OpenSRS
Operational
Domain Registrar » ROTLD
Operational

12 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking ROMARG Core » Backup Servers, ROMARG Core » Client Area, ROMARG Core » Cloud SpamExperts, ROMARG Core » Dns Servers, ROMARG Core » Email/Ticket Support, ROMARG Core » Live Chat Support, ROMARG Core » Phone Support, ROMARG Core » Web Sites, Servere Dedicate Administrate, Servere VPS, Shared Enduser, Shared Reseller.

See all of them free

Component statuses may change independently during partial outages.

Recent ROMARG Outages & Incidents

Incident history from the official ROMARG status page, including resolution updates.

Alerta de securitate PHP (CVE-2026-109618 / CVE-2026-109619)Resolved Oct 22, 2026 · 49h 41mResolved

UPDATE FINAL - consideram acest incident incheiat. Versiunile PHP instalate pe serverele administrate beneficiaza de update-urile de securitate. --- [2026-10-23T10:52:16.815+03:00] (identified) UPDATE - Pentru toate servere dedicate administrate ce ruleaza Cloudlinux versiunile PHP instalate de la 5.4 pana la 8.5 au fost securizate. Update-urile de securitate au venit de la Cloudlinux si au pastrat numele de versiune vechi. Lucram la auditul final pentru serverele ce ruleaza CentOS si Almalinux. --- [2026-10-22T16:59:51.151+03:00] (identified) UPDATE - Pentru toate servere shared shared enduser si reseller versiunile PHP instalate de la 5.4 pana la 8.5 au fost securizate. Update-urile de securitate au venit de la Cloudlinux si au pastrat numele de versiune vechi. Lucram in continuare pentru serverele virtuale si dedicate. --- [2026-10-22T12:52:33.108+03:00] (identified) Incepand cu 21.10.2026 ora 00:01 am fost notificati de partenerii nostri despre identificarea a doua vulnerabilitatii critice în PHP (CVE-2026-109618 si CVE-2026-109619), ambele cu scor de severitate 9.2 din 10. Ele permit unui atacator să execute cod pe serverul web printr-o simplă cerere HTTP, fara autentificare si fara a exploata vreun plugin sau o eroare a aplicatiei, problema este la nivel de PHP toate versiunile fiind afectate. In ultimele 24 de ore la ROMARG am lucrat activ pentru a implementa masuri preventive de protectie pana la publicarea versiunilor updatate de PHP. In ultimele ore Cloudlinux, cPanel respectiv AdminBolt au reusit sa puna la dispozitie update-urile necesare, iar aceastea sunt in curs de a fi instalate pe toate serverele administrate de ROMARG. Trebuie sa stiti ca cel putin pana la acest moment, Cloudlinux a fost folosit backporting, fara sa schimbe versiunea instalata. Vom reveni cu update final dupa finalizarea update-urilor.

ROMARG Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a ROMARG incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live ROMARG Outage Reports

Problems reported by engineers using ROMARG. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No ROMARG problems reported yet.

Something wrong with ROMARG on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About ROMARG

ROMARG's status page at status.romarg.com lists 15 components, such as Eurid, OpenSRS and ROTLD. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on ROMARG's side or yours.

ROMARG Status FAQ

Is ROMARG down right now?

The verdict at the top of this page comes from the latest poll of the official ROMARG status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if ROMARG is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until ROMARG recovers.

How do I check ROMARG uptime history?

PulsAPI tracks ROMARG uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever ROMARG changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect ROMARG outages?

PulsAPI reads the official ROMARG status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual ROMARG components?

Yes. PulsAPI monitors 15 individual ROMARG components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when ROMARG goes down?

Yes. Create a free account and subscribe to ROMARG: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with ROMARG to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot ROMARG problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor ROMARG?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so ROMARG plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track ROMARG with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services