Service status & outage reports

Is Firsthand down?

Check Firsthand availability, incident history, downtime reports, and website performance.

https://www.firsthand.ai ↗
Provider reports operational

Mapped components are operational in the latest status update; individual experiences can vary.

0 recorded outage reports · rolling 24 hours

Estimated activity checked · Text version ↗

My watchlist

Service disruption activity for Firsthand

Last 24 hours
0501002026-11-10T04:50:00.000Z: 0.02026-11-10T05:00:00.000Z: 0.02026-11-10T06:00:00.000Z: 0.02026-11-10T07:00:00.000Z: 0.02026-11-10T08:00:00.000Z: 0.02026-11-10T08:10:00.000Z: 0.02026-11-10T09:00:00.000Z: 0.02026-11-10T09:10:00.000Z: 0.02026-11-10T10:00:00.000Z: 0.02026-11-10T10:20:00.000Z: 0.02026-11-10T11:00:00.000Z: 0.02026-11-10T11:30:00.000Z: 0.02026-11-10T12:00:00.000Z: 0.02026-11-10T12:30:00.000Z: 0.02026-11-10T13:00:00.000Z: 0.02026-11-10T13:40:00.000Z: 0.02026-11-10T14:00:00.000Z: 0.02026-11-10T14:50:00.000Z: 0.02026-11-10T15:00:00.000Z: 0.02026-11-10T15:50:00.000Z: 0.02026-11-10T16:00:00.000Z: 0.02026-11-10T17:00:00.000Z: 0.02026-11-10T18:00:00.000Z: 0.02026-11-10T18:10:00.000Z: 0.02026-11-10T19:00:00.000Z: 0.02026-11-10T19:10:00.000Z: 0.02026-11-10T20:00:00.000Z: 0.02026-11-10T20:20:00.000Z: 0.02026-11-10T21:00:00.000Z: 0.02026-11-10T21:30:00.000Z: 0.02026-11-10T22:00:00.000Z: 0.02026-11-10T22:30:00.000Z: 0.02026-11-10T23:00:00.000Z: 0.02026-11-10T23:40:00.000Z: 0.02026-11-11T00:00:00.000Z: 0.02026-11-11T00:40:00.000Z: 0.02026-11-11T01:00:00.000Z: 0.02026-11-11T01:50:00.000Z: 0.02026-11-11T02:00:00.000Z: 0.02026-11-11T03:00:00.000Z: 0.02026-11-11T03:50:00.000Z: 0.024h ago18h ago12h ago6h agoNow
Disruption activity index (0–100). Published incidents and repeated check failures carry more weight than emerging problem patterns. This is not a report count or percentage of affected users. Gaps have no observations; connecting lines do not add measurements.

Observed disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.

Latest observation: 2026-11-11 03:56:43 UTC. Refreshes automatically while this page is visible.

No user-submitted outage reports in the last 24 hours.

Firsthand outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

DecJanFebMarAprMayJunJulAugSepOctNov
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Firsthand website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-11-11 03:02:08 UTC.

Checked address: https://www.firsthand.ai/

DNS lookup: 14 ms · TCP connection: 2 ms · TLS handshake: 8 ms. Certificate expires 2027-01-26; trusted connection: yes.

100%
Successful website checks (24h)
21 successful / 21 measurable checks

162 ms
Median response time

230 ms
95th percentile response time

Successful website response times, 0 to 293 milliseconds293 ms0 ms2026-11-10T04:54:30.000Z: 89 ms2026-11-10T06:00:17.000Z: 134 ms2026-11-10T07:06:57.000Z: 162 ms2026-11-10T08:13:43.000Z: 167 ms2026-11-10T09:19:58.000Z: 127 ms2026-11-10T10:26:40.000Z: 230 ms2026-11-10T11:33:35.000Z: 197 ms2026-11-10T12:39:25.000Z: 106 ms2026-11-10T13:45:22.000Z: 160 ms2026-11-10T14:52:17.000Z: 217 ms2026-11-10T15:59:12.000Z: 126 ms2026-11-10T17:05:07.000Z: 124 ms2026-11-10T18:11:57.000Z: 182 ms2026-11-10T19:18:51.000Z: 293 ms2026-11-10T20:24:32.000Z: 217 ms2026-11-10T21:30:24.000Z: 213 ms2026-11-10T22:36:58.000Z: 150 ms2026-11-10T23:43:54.000Z: 198 ms2026-11-11T00:49:45.000Z: 144 ms2026-11-11T01:55:21.000Z: 181 ms2026-11-11T03:02:08.000Z: 82 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Firsthand official status · fetched 2026-11-11 03:56:43 UTC

2 mapped components · 0 reporting problems
ComponentProvider status
Prompt Serveroperational
Firsthand UIoperational

Official incident timeline

Campaigns experiencing issues due to GCP outage · resolved · 2026-03-12T18:20:13Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    The GCP incident has been resolved and all campaign service functionality has fully recovered.

  2. · monitoring

    We are experiencing intermittent issues serving campaigns, tracking impressions, and loading images due to a service outage with our cloud partner. We are monitoring the situation and will provide updates once service is restored.

Recovery tracker

No recent recovery can be established from available evidence.

0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

More successful checks are needed to establish a response-time baseline.

Recent median: unknown · Earlier median: 162 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

No recent emerging problem patterns are available for this service.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Firsthand.

GitHub official status · 2026-11-11 04:06:49 UTC

No active incidents recorded.

About Firsthand status on Iszdown

Check Firsthand availability, incident history, downtime reports, and website performance.

This page combines the available Firsthand report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

2 product-matched official components are listed above. Latest public website measurement: 2026-11-11T03:02:08.000Z.

Visit the official Firsthand website · Official provider status · How it works

What to check when Firsthand is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Firsthand will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Firsthand is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Firsthand outage history

No product-matched official incidents have been archived for this service in the displayed history. This does not establish that it has never had an outage. See the daily calendar for other available evidence.

Frequently asked questions about Firsthand

Is Firsthand down right now?

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T04:08:34.000Z.

How many Firsthand outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Firsthand show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Firsthand feature.

When was Firsthand status last updated?

The latest status observation was 2026-11-11T03:56:43.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Firsthand had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Firsthand or report a problem?

Use “Watch this service” to save Firsthand in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to Firsthand

Check a related product separately; its status can differ from Firsthand.

Firsthand