Is FieldEdge Down?

No — FieldEdge is up

FieldEdge's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 1006 ms

Right now

The verdict is the worse of these two. How we decide

FieldEdge's status page

status.fieldedge.com · read 3 minutes ago · checked every 3 minutes

Operational

FieldEdge's components, as its status page reports them
Component	Status
Site East	Operational
Site West	Operational
Mobile	Operational

Open their status page

FlareWarden checks

fieldedge.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 1006 ms
Checked: 2 hours ago

By region

Chicago reachable, 223 ms
Johannesburg reachable, 1858 ms
London reachable, 528 ms
Los Angeles reachable, 508 ms
San Jose reachable, 634 ms
Singapore reachable, 1634 ms
Sydney reachable, 1565 ms
Tokyo reachable, 1105 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	47 ms	41 ms	43 ms	156 ms
Johannesburg	369 ms	244 ms	264 ms	1121 ms
London	31 ms	77 ms	110 ms	297 ms
Los Angeles	60 ms	60 ms	108 ms	314 ms
San Jose	67 ms	71 ms	97 ms	309 ms
Singapore	190 ms	237 ms	257 ms	922 ms
Sydney	297 ms	206 ms	223 ms	935 ms
Tokyo	67 ms	169 ms	189 ms	595 ms

We check that fieldedge.com loads, not every feature behind it. Test it yourself

History

Incidents FieldEdge reported

Since Oct 22, 16 days · from status.fieldedge.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

FieldEdge website availability

Measured by FlareWarden · fieldedge.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 841ms

Last 30 days

17-day clean streak

Oct 8 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of fieldedge.com from multiple regions every 6 hours. FieldEdge's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What FieldEdge does

FieldEdge is field service management software for HVAC, plumbing, electrical and other home service contractors, part of Xplor Technologies. Office staff schedule and dispatch technicians, manage customers and sync financials to QuickBooks in FieldEdge Web. Technicians use the FieldEdge Mobile app to see their schedule and job details, generate quotes, create invoices and take payments on site, and the app stays in sync with the web app.

What an outage looks like

Lists, customer records and the dashboard load slowly, logins fail on web and mobile, or the mobile app is slow to log in or out. Several outages began at Microsoft Azure: in July 2026 a West region fault disrupted Twilio calls and texts, online booking, the leads panel, Proposal Pro, DocuSign and PDF generation. In December 2024 affected accounts were made read-only, able to view records but not save changes.

What to do about it

Open status.fieldedge.com, which lists Site East, Site West and Mobile as separate rows; some incidents touched only one. If calls, texts or emails fail while scheduling works, suspect an integration: in the October 2025 AWS outage FieldEdge said its core web and mobile service did not rely on AWS, while Twilio and SendGrid did. Report problems that outlast a fix through the FieldEdge Support help center linked from fieldedge.com.

Is it down for everyone, or just you?

If this page says FieldEdge is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

FieldEdge outage FAQ

Does the FieldEdge mobile app work offline?

Partly, in the newer app. Release notes for FieldEdge Mobile 2.0 in 2026 added offline mode for work orders, forms and equipment, so technicians can keep working without an internet connection. The FieldEdge Mobile 1.0 listing does not mention offline use. These notes describe the phone losing its connection; they do not say how the app behaves when FieldEdge's own servers are down.

Will technicians lose work entered on the mobile app?

Not usually, but uninstalling the app before it has synced can lose data. In an August 2024 incident some members could not log out or push data to the server, and FieldEdge said reinstalling could lose the last transaction, such as invoice items or a status change. It advised logging out and back in first, and reinstalling only if that failed.

Is it FieldEdge or Microsoft Azure?

Often Azure. In July 2026 FieldEdge tied a disruption of nearly five hours on Site West to an Azure West region network issue, and in December 2024 it worked with Microsoft through an Azure fault that blocked logins on the east coast and in the south central US. In September 2024 customers whose AT&T connections reached Microsoft services had trouble opening the application.

Does the status page cover FieldEdge ESC?

It does not list ESC. The status page has rows only for Site East, Site West and Mobile. FieldEdge sells ESC as server-based software for home service contractors, and fieldedge.com sends ESC customers to a separate ESC Support help center rather than the FieldEdge one, so an ESC problem is a question for that support team.

Why are FieldEdge emails to customers not arriving?

Usually it is the recipient's email filtering. During a September 2026 incident FieldEdge said messages were leaving its platform and being accepted by its provider, SendGrid, but some were delayed or blocked by third-party email security providers, including spam filtering for Microsoft Exchange users. It closed the incident on September 29, 2026, noting individual recipients could still filter messages.

How we measure this

We request FieldEdge's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where FieldEdge publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of FieldEdge itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when FieldEdge goes down

We check FieldEdge every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required