iSAMS logo

Is iSAMS Down?

SaaSLive status, outages, and incident history

No. iSAMS is up right now.

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

OperationalChecked 3m agoLive · every 60s

Know the moment iSAMS breaks

iSAMS 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.

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

Status report

iSAMS Status Summary

As of 19:22 UTC on 14 November 2026, iSAMS is operational. PulsAPI checked iSAMS's official status page and found 25 of 25 components operational, with no active incidents. The latest incident, "Microsoft 365 Outage", was on Nov 13, 2026 and lasted 6h 5m.

Cite as: PulsAPI, “iSAMS status”, checked 14 November 2026, 19:22 UTC. https://www.pulsapi.com/services/isams

iSAMS Component Status

The main iSAMS systems on this page. All 25 are operational right now.

25operational
3rd Party Services (Application) » Cloud SMTP Service
Operational
3rd Party Services (Application) » Push Notification Services
Operational
3rd Party Services (Application) » SMS Gateway · EU & ROW Inbound
Operational

22 more components tracked

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

Also tracking 3rd Party Services (Operations) » Central CRM API, 3rd Party Services (Operations) » Finance Portal & API, 3rd Party Services (Operations) » iCommunity Portal, 3rd Party Services (Operations) » Ideas Portal, 3rd Party Services (Operations) » Identity Portal, 3rd Party Services (Operations) » Infrastructure Monitoring Service, 3rd Party Services (Operations) » iUniversity, 3rd Party Services (Operations) » Webinar Service, 3rd Party Services (Support) » Agent Interface, 3rd Party Services (Support) » Online Chat, 3rd Party Services (Support) » Support Website, 3rd Party Services (Support) » Telephony, and 10 more.

See all of them free

Component statuses may change independently during partial outages.

Recent iSAMS Outages & Incidents

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

Microsoft 365 OutageResolved Nov 13, 2026 · 6h 5mResolved

Dear Customers, Regarding todays issue with Microsoft we understand that service is beginning to return to normal and as such are closing this alert down. However if in your region you are yet to return to full functionality please continue to use our chat/phone/ticket form to contact us, rather than emails. Once again we apologise for the inconvenience caused. --- [2026-11-13T10:25:35.018+00:00] (monitoring) Dear Customer, Regarding the issues currently being experienced when attempting to access Outlook and Microsoft 365 services. This is a known widespread issue affecting Microsoft's infrastructure, with users potentially experiencing difficulties accessing Outlook (both desktop and web versions), connecting to their mailboxes, and sending or receiving emails. Other Microsoft 365 services that rely on Exchange Online may also be affected. Microsoft has acknowledged the incident and is actively investigating, with work underway to restore normal service. Initial improvements have been reported, and Microsoft continues to monitor stability and implement further changes. We will continue to monitor the situation and provide further updates as Microsoft shares additional information. You can also follow Microsoft's latest updates via their Microsoft 365 Service Status page - https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect. We apologise for any inconvenience caused and appreciate your patience. --- [2026-11-13T08:25:08.213+00:00] (monitoring) Dear Customers, We are aware of the ongoing Microsoft issue and currently we recommend that customers either use our chat/phone/ticket form to contact us, rather than emails as communications may be interrupted. We will continue to share any updates regarding this on the status page.

Problem with API KeysResolved Nov 4, 2026 · 24h 5mResolved

Dear Customers, Regarding yesterdays issue that has impacted the API Keys and consequently the services that rely on them. We are pleased to share that a following yesterdays mitigation that was deployed to restore service the permanent fix will follow in the next release due tonight. Please note: Engineering anticipate that the update will complete overnight and no action is required by you. When an update is available it will be displayed in the "Notices" area in the iSAMS Control Panel. An update may take a couple of days to reach all customers. Once again we apologise for the inconvenience caused. --- [2026-11-04T17:52:16.251+00:00] (monitoring) Dear Customers, Regarding todays issue that has impacted the API Keys and consequently the services that rely on it. We are pleased to share that a mitigation has been deployed to restore service and a permanent fix will follow in the next update due 5.11.2026 Please note: Engineering anticipate that the update will complete overnight and no action is required by you. When an update is available it will be displayed in the "Notices" area in the iSAMS Control Panel. An update may take a couple of days to reach all customers. Once again we apologise for the inconvenience caused. --- [2026-11-04T15:59:49.183+00:00] (investigating) Dear Customers, We have identified an issue that has impacted the API Keys, and consequently the services that rely on it. Our Engineering Team have been engaged and are working towards a resolution to restore service as soon as possible. We are sorry for the inconvenience this has caused and will continue to share any updates via the status page.

27/10/2026 - iSAMS Performance IssueResolved Oct 27, 2026 · 6h 27mResolved

Dear customers, The following update has been sent to customers that have raised tickets: Our investigation has found that FortiGate security inspection (SSL/TLS inspection and/or Application Control) is interfering with HTTPS/TLS traffic between your users and Cloudflare infrastructure used by iSAMS. Bypassing Forti inspection for the iSAMS traffic has restored service for multiple affected schools. Please note: this issue is caused by the FortiGate appliance or / and it's configuration. Because any configuration changes must be made on your firewall, resolving the issue is outside our ability and responsibility. Your school IT team (or your Fortinet support/partner) can implement any configuration changes. Our recommendation at this time is to add the following to the FortiGate allowed list; Your iSAMS domain wildcard: either *.isamhosting.cloud or *.isams.cloud (whichever your school uses) Your identity provider domains if they are being filtered, eg google, microsoft etc... *.cloudflare.com Below is the solution one school shared with us that worksaround the issue, it is your schools decision if you decide to also apply the same workaround. Please be aware disabling SSL inspection reduces visibility for those domains and therefore recommend you limit exemptions to the exact domains required. Add a separate policy for each iSAMS URL on HTTPS with no SSL inspection. Place those new policies above any staff internet policies. IPS and Anti-virus to remain in place. --- [2026-10-27T12:11:04.200+00:00] (investigating) Dear customers, Are team are continuing to investigate this issue and updates are being provided via our ticketing system. Please accept our apologies for any inconvenience. --- [2026-10-27T08:39:06.561+00:00] (investigating) Dear customers, We are aware of an issue affecting some of our customers meaning that they are unable to access iSAMS. Our investigation team are reviewing this now and treating this as an urgent priority. Please accept our apologies for any inconvenience.

iSAMS Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a iSAMS 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 iSAMS Outage Reports

Problems reported by engineers using iSAMS. 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 iSAMS problems reported yet.

Something wrong with iSAMS on your end?

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

About iSAMS

Is iSAMS down? Its official status page at status.isams.com reports on 25 components, including Cloud SMTP Service (Outbound), Push Notification Services (Apple & Google) and SMS Gateway (EU & ROW Inbound). PulsAPI checks it every few minutes and can alert you when iSAMS reports an incident.

iSAMS Status FAQ

Is iSAMS down right now?

The verdict at the top of this page comes from the latest poll of the official iSAMS 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 iSAMS 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 iSAMS recovers.

How do I check iSAMS uptime history?

PulsAPI tracks iSAMS 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 iSAMS changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect iSAMS outages?

PulsAPI reads the official iSAMS 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 iSAMS components?

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

Can I get alerts when iSAMS goes down?

Yes. Create a free account and subscribe to iSAMS: 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 iSAMS 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 iSAMS problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor iSAMS?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so iSAMS 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 iSAMS 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