Status updated

All Systems Operational
Jobber logo

Jobber down?

Jobberstatus.net is the public status page for Jobber, the field service management software used by home service businesses such as landscapers, cleaners, plumbers and HVAC contractors. The page shows the current operational status of Jobber's web app, mobile apps, client hub, online booking, payments, messaging and integrations. It posts information about ongoing incidents, degraded performance and scheduled maintenance, plus a history of past issues. Service business owners and their teams use it to check whether a problem is on Jobber's side and subscribe to updates.

Jobber status preview image

I have a problem with Jobber

Select the type of problem you're facing to help us and other users.

Recent User Report Trends for Jobber

Aggregated reports in the last 48 hours.

No user reports about Jobber in the last 48 hours.

uptimecard

View live report trends

Add your report to help, or tap to skip

What is Jobber's current status?

All systems are operational

No active incidents reported.

Incident history: past 7 days

times in UTC

Today

No incidents reported.

Yesterday

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

No incidents reported.

Oct 28, 2026

No incidents reported.

Oct 27, 2026

No incidents reported.

Oct 26, 2026

No incidents reported.

User Reports for Jobber

Recent issues reported by users from around the world.

No user reports for Jobber in the last 30 days.

Experiencing an issue? Add your report:

Stop refreshing this page

We'll email you the moment Jobber goes down — and again when it's back.

About Jobber & Technical Insights

What this service does and the technologies behind it.

Loading tech map…
Read the tech stack as text▾

Overview: A lean, CDN-delivered status page stack built on Atlassian Statuspage with jQuery/Bootstrap frontend and AWS edge delivery, prioritizing uptime communication over bespoke engineering.

What stands out

  • The stack is dominated by hosted status page infrastructure rather than custom application code.
  • Heavy reliance on third-party CDNs (CloudFront, cdnjs, Cloudflare) suggests a focus on fast global delivery and low origin load.
  • Presence of reCAPTCHA, RSS, and Google Tag Manager points to customer communication, spam protection, and analytics as key operational concerns.
  • jQuery, Bootstrap, and Lodash are legacy-friendly choices that prioritize broad browser compatibility and rapid UI development.

Technologies jobberstatus.net uses

  • Atlassian Statuspage — Hosted status page for Jobber; communicates service health and incident updates to customers.
  • Lodash — Utility library for JavaScript data manipulation in status page frontend.
  • Amazon CloudFront — Delivers status page assets and content globally with low latency via AWS CDN.
  • Bootstrap — Responsive UI framework for layout and components.
  • Font Awesome — Provides iconography for status indicators, UI buttons, and component states.
  • Cloudflare — DNS, CDN, and security proxy in front of the site.
  • Amazon Web Services — Underlying cloud infrastructure for hosting and CDN.
  • jQuery — JavaScript library for DOM manipulation and events.
  • core-js — Polyfills modern JavaScript for older browsers.
  • Google Analytics — Tracks visitor behavior and status page usage.
  • RSS — Provides incident feed for status subscribers.
  • cdnjs — Serves frontend libraries like jQuery, Font Awesome, and Lodash to reduce origin load.
  • Twitter typeahead.js — Powers autocomplete/search on status page, likely for incident or component lookup.
  • Webpack — Bundles and optimizes frontend assets.
  • Google Code Prettify — Syntax-highlights code snippets, possibly in status page API documentation or incident notes.
  • reCAPTCHA — Protects forms from spam, likely subscription or contact.
  • HSTS — Enforces HTTPS connections.
  • Google Tag Manager — Manages analytics and marketing tags.

How these technologies work together

  • Bootstrap requires jQuery — Bootstrap's JavaScript components require jQuery for interactive UI elements like modals.
  • Google Analytics integrates with Google Tag Manager — Google Tag Manager deploys and manages Google Analytics tracking across the site.
  • Amazon CloudFront runs on Amazon Web Services — CloudFront is AWS's CDN service, part of the same cloud platform.
  • Lodash requires Webpack — Webpack bundles Lodash modules into optimized chunks for the production build.
  • cdnjs requires Font Awesome — Font Awesome icons are loaded from cdnjs, so cdnjs is required for those icons.
  • cdnjs requires jQuery — jQuery is loaded from cdnjs, so cdnjs is required for DOM operations.
  • Amazon CloudFront requires Atlassian Statuspage — Atlassian Statuspage serves its status pages through CloudFront for fast global delivery.
  • Bootstrap requires cdnjs — Bootstrap CSS and JavaScript assets are loaded from cdnjs, relying on the CDN.
  • cdnjs requires Lodash — Lodash is served from cdnjs, making cdnjs a dependency for utility functions.
  • Cloudflare requires HSTS — Cloudflare enforces HSTS headers to force secure HTTPS connections for visitors.
  • Bootstrap works alongside Font Awesome — Font Awesome icons pair with Bootstrap components for consistent UI iconography.
  • Atlassian Statuspage integrates with RSS — Statuspage generates RSS feeds for incident updates, allowing users to subscribe to service alerts.
  • core-js requires Webpack — Webpack bundles core-js polyfills into the frontend build for older browser support.
  • jQuery requires Webpack — Webpack bundles jQuery and its dependencies for the production frontend bundle.
  • Bootstrap works alongside Twitter typeahead.js — Typeahead enhances Bootstrap forms with autocomplete for status page search.
  • Atlassian Statuspage integrates with Google Code Prettify — Prettify formats code blocks in status page incident notes or API docs.
  • Atlassian Statuspage integrates with reCAPTCHA — Statuspage subscription forms use reCAPTCHA to block spam and abuse.
  • Amazon CloudFront overlaps with Cloudflare — Both Cloudflare and CloudFront provide CDN and security, overlapping in purpose.
  • jQuery works alongside Lodash — Lodash and jQuery are both used for frontend utility, often paired together.
Analytics
Google Tag ManagerGoogle Tag Manager
Google AnalyticsGoogle Analytics
Other
WebpackWebpack
Google Code PrettifyGoogle Code Prettify
RSSRSS
Servers
CloudflareCloudflare
Atlassian StatuspageAtlassian Statuspage
cdnjscdnjs
Amazon Web ServicesAmazon Web Services
Amazon CloudFrontAmazon CloudFront
Web Development
Twitter typeahead.jsTwitter typeahead.js
HSTSHSTS
BootstrapBootstrap
Atlassian StatuspageAtlassian Statuspage
core-jscore-js
jQueryjQuery
Font AwesomeFont Awesome
reCAPTCHAreCAPTCHA
LodashLodash

Trust & Safety Checks

Public registration, DNS and certificate records UptimeCard checked independently for the domain jobberstatus.net.

Domain name active since 2014

jobberstatus.net has been a registered domain since December 2014 — 11 years at the same web address.

Domain lock enabled

The registry blocks unauthorised transfers, deletion and record changes, so the domain cannot be hijacked.

DNS managed by GoDaddy

2 nameservers answer for this domain, so it stays reachable even if one goes offline.

Hosted by Amazon.com, Inc.

Served from professional infrastructure located in Canada.

Records last verified August 2026.

How to fix Jobber not working

Jobber is field service software for home service businesses, covering scheduling, quotes, invoices and client communication. This is Jobber's public status page, so check it first. An active incident here means the problem is on Jobber's side. If everything shows as working, the cause is more likely your sign-in, your device or a setting, and the steps below help you narrow it down.

Jump to what you are seeing

Website Down

The Jobber web app does not load for you.

  1. Open the app in a private window and on another network.
  2. Check this status page for an active incident affecting the web app.
  3. If it loads on another network, your firewall or proxy is the cause.

Mobile App Down

The mobile app will not open, or does not sync your jobs.

  1. Close the app and open it again, and check the phone has a connection.
  2. Update the app from your app store.
  3. Sign out and back in. If the web app works but the app does not, report it with your phone model and app version.

Login Failed

Sign-in is refused. Team members have their own logins, so check which account you are using.

  1. If the message says the password is wrong, reset it and check spam.
  2. Ask your account owner to confirm your user is active and has the right permissions.
  3. Try a private window to rule out an old session.

Payment Issues

A client payment does not take, or it shows the wrong status.

  1. Check the payment method on the invoice is valid, and that the client's bank has not blocked it.
  2. Check the payment status on the invoice before asking the client to pay again.
  3. If a payment failed with no reason shown, send the invoice number and the time to support.

Scheduling Errors

Jobs will not schedule, or they show at the wrong time or for the wrong team member.

  1. Check the team member's working hours and time zone.
  2. Check the job's address and visit time are complete.
  3. Reload the schedule, since an old view can show old times.

Client Hub Down

Clients cannot open their hub to view or pay for work.

  1. Ask a client to try a private window and another device, and to send you the exact message they see.
  2. Check the client hub link you sent is the current one.
  3. Check this status page for a client hub incident.
  4. If the hub is down for everyone, let clients know how to reach you until it is back.

Still not working?

If it still does not work and this status page shows no incident, contact your Jobber account admin first. If they cannot find the cause, contact Jobber support through the help option in the app or on the Jobber website. Have your business name, the job or invoice number, the exact error text, and the time it started with your time zone. Live incident updates are on www.jobberstatus.net.

Most field-service problems come from a sign-in, a device or a schedule setting, and they usually clear once that is corrected. The status page shows live incidents, so you can see when Jobber reports an issue.

Frequently asked questions about Jobber

Is Jobber down right now?

No. Based on the latest status data on this page, Jobber (jobberstatus.net) is up and running normally. The most recent incident, "Performance issues loading Jobber", was resolved (last update Sep 11, 2026).

What should I do if Jobber is not working for me?

First rule out your side: reload the page, try another browser or device, clear the cache and cookies for jobberstatus.net, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.

What was the most recent Jobber incident?

The most recent incident on record is "Performance issues loading Jobber", last updated on Sep 11, 2026. It has been resolved.

How many people reported problems with Jobber recently?

No user reports about Jobber were submitted in the last 48 hours.

How do I report a problem with Jobber?

Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.

Where is the official Jobber status page?

The official status page for Jobber is www.jobberstatus.net.

Related Keywords

Common themes, topics and technologies associated with jobberstatus.net.

status pagesystem monitoringincident managementservice statusoutage notificationsreal-time monitoringsystem performanceservice availabilityincident reportingmaintenance statusweb applicationmobile applicationapi statussupport servicesthird-party servicesjobber paymentsemail servicestext messagingquickbooks integrationweb application subscriptionsai receptionistoperational statusdegraded performancepartial outagemajor outagemaintenance updateshistorical dataservice interruptionsstatus notificationsemail alertssms notificationsslack integrationwebhook notificationssystem reliabilityuptime monitoringservice healthperformance trackingincident resolutionservice disruption