Skip to main content
TeamSnap logo

Is TeamSnap Down?

No — TeamSnap is up

Reachable from all 8 checked regions

Average response time: 1325ms

Last checked · checks run every 6 hours

Official status page: https://status.teamsnap.com

TeamSnap uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1182ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: no data
Sep 30: no data
Oct 1: 100.00% uptime, 22 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 24 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
953ms
DNS 168ms TCP 8ms TLS 21ms TTFB 835ms
lhr
916ms
DNS 56ms TCP 1ms TLS 13ms TTFB 765ms
nrt
1986ms
DNS 249ms TCP 1ms TLS 10ms TTFB 1807ms
ord
309ms
DNS 103ms TCP 1ms TLS 24ms TTFB 285ms
sin
2708ms
DNS 80ms TCP 2ms TLS 12ms TTFB 2467ms
sjc
901ms
DNS 126ms TCP 16ms TLS 10ms TTFB 753ms
syd
2391ms
DNS 242ms TCP 1ms TLS 9ms TTFB 2151ms
yyz
443ms
DNS 114ms TCP 12ms TLS 26ms TTFB 402ms

What TeamSnap does

TeamSnap is a youth sports management platform used by coaches, team managers, parents, clubs and leagues. Teams rely on it for schedules, availability, rosters, Team Chat and alerts; clubs and leagues use it for registration, payments, tournaments and websites. It runs as the TeamSnap iOS and Android apps, the go.teamsnap.com web app, hosted team and league websites, and the separate TeamSnap ONE platform.

What an outage looks like

The app will not load schedules or rosters, the login page fails to open, or the iOS app shows Error 3840, which TeamSnap's help center says usually means something is down on its end. Game and event updates, alerts and Team Chat messages arrive late or not at all. Hosted team and league websites on teamsnapsites.com can go offline while the apps keep working.

What to do about it

Check status.teamsnap.com, which tracks the iOS app, Android app, API/Mobile Apps, Team/League Website, Email/SMS Delivery, Push Notifications, Payments, Registrations and TeamSnap ONE separately, and subscribe by email, Slack or RSS. If only the app fails, try the website, or the reverse. Reach families directly about game-day changes until messages flow. For account help, use the help widget at the bottom right when logged in.

Is it down for everyone, or just you?

If this page says TeamSnap 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

Cloudflare
Cloudflare
AWS
AWS
R
Remind
C
ClassDojo

TeamSnap outage FAQ

Is TeamSnap down for everyone or just me?
Compare the component you use on status.teamsnap.com with what you see. If TeamSnap shows it operational and the site answers here, the fault is more likely local. TeamSnap's help center ties iOS errors 1001, 1003, 1005 and 1200 to network problems and suggests restarting the Wi-Fi router, resetting network settings, or reinstalling the app. Error 3840, by contrast, usually means a problem on TeamSnap's side.
Does a Cloudflare or AWS outage affect TeamSnap?
Yes. TeamSnap's own status page has attributed login-page failures to outages at Cloudflare, which it calls its network infrastructure provider, and platform slowdowns to an AWS outage. In those incidents TeamSnap said service would resume once the provider recovered, so if Cloudflare or AWS is reporting a major incident, expect TeamSnap logins or page loads to suffer until that provider's fix lands.
Why am I not getting TeamSnap notifications?
Push notifications need the latest TeamSnap app, an active login on the device, an internet connection, and notifications enabled both in the app's preferences and in the phone's settings. TeamSnap states that push notifications are in-app messages and are not delivered by SMS text. Its status page tracks Push Notifications and Email/SMS Delivery as separate rows, so one can fail while the other works.
Does the TeamSnap website work when the app is down?
Often, yes. TeamSnap monitors its iOS app, Android app, API/Mobile Apps and Team/League Website as separate components, and some past incidents affected only the website side, such as login-page failures during Cloudflare outages. Opening TeamSnap in a browser is worth trying when the app will not load, though TeamSnap's help center notes that the mobile browser version lacks Team Chat and TeamSnap Live.
How do I contact TeamSnap support during an outage?
Use the help widget in the bottom right corner of the screen when you are logged in. TeamSnap supports customers mainly by email and chat, with limited phone support. Its help center lists admin support from 8 AM to 6 PM CST and team support from 8 AM to 10 PM CST, seven days a week. For a platform-wide outage, the status page is the faster source of updates.

How we measure this

  • We request TeamSnap's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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. We only change the 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 TeamSnap publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when TeamSnap goes down

This page refreshes every 6 hours. 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