Skip to content

Outage tracker / Snapchat

Is Snapchat down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Snapchat pass from all 10 regions we check.

As of Nov 5, 2026, 2:42 PM UTC, RealUptime's checks of Snapchat passed in all 10 regions that returned a reading.

Front-door checks

Our checks of Snapchat did not fail from two or more distant regions in the 77 days we have checked it (since Aug 20, 2026). This does not show Snapchat works for users.

Email me when our checks of Snapchat fail from two or more distant regions

One email when our checks of Snapchat fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Snapchat's official status.

our check readinglive · checked Nov 5, 2026, 2:42 PM UTC
US-East570 msChecks passing
US-West1208 msChecks passing
Europe965 msChecks passing
Asia-Pacific1896 msChecks passing
US-Central723 msChecks passing
Canada766 msChecks passing
UK189 msChecks passing
Southeast Asia1204 msChecks passing
Australia3024 msChecks passing
South America1163 msChecks passing
their status pagetheir claim, not our reading

Snapchat publishes no status feed we can read, so the only reading here is our check reading on the left.

Snapchat response time, by region

US-East
1.2sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 641ms2026-10-08 UTC: p95 580ms2026-10-09 UTC: p95 594ms2026-10-10 UTC: p95 650ms2026-10-11 UTC: p95 684ms2026-10-12 UTC: p95 561ms2026-10-13 UTC: p95 777ms2026-10-14 UTC: p95 646ms2026-10-15 UTC: p95 775ms2026-10-16 UTC: p95 773ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 917ms2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 893ms2026-10-30 UTC: p95 923ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 988ms2026-10-08 UTC: p95 807ms2026-10-09 UTC: p95 800ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 883ms2026-10-13 UTC: p95 834ms2026-10-14 UTC: p95 925ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 867ms2026-10-17 UTC: p95 745ms2026-10-18 UTC: p95 863ms2026-10-19 UTC: p95 926ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 539ms2026-10-08 UTC: p95 452ms2026-10-09 UTC: p95 430ms2026-10-10 UTC: p95 541ms2026-10-11 UTC: p95 589ms2026-10-12 UTC: p95 456ms2026-10-13 UTC: p95 316ms2026-10-14 UTC: p95 412ms2026-10-15 UTC: p95 529ms2026-10-16 UTC: p95 444ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.4s2026-10-08 UTC: p95 2.4s2026-10-09 UTC: p95 2.1s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.2s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.4s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 3.4s2026-10-21 UTC: p95 3.1s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 3.2s2026-10-25 UTC: p95 3.4s2026-10-26 UTC: p95 3.9s2026-10-27 UTC: p95 3.6s2026-10-28 UTC: p95 3s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 3.3s2026-11-01 UTC: p95 3.3s2026-11-02 UTC: p95 3.6s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
933msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 525ms2026-10-08 UTC: p95 604ms2026-10-09 UTC: p95 598ms2026-10-10 UTC: p95 627ms2026-10-11 UTC: p95 641ms2026-10-12 UTC: p95 540ms2026-10-13 UTC: p95 512ms2026-10-14 UTC: p95 715ms2026-10-15 UTC: p95 581ms2026-10-16 UTC: p95 652ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 948ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 985ms2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 951ms2026-10-30 UTC: p95 974ms2026-10-31 UTC: p95 929ms2026-11-01 UTC: p95 876ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 933ms
Oct 7Oct 21Nov 5
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 712ms2026-10-08 UTC: p95 551ms2026-10-09 UTC: p95 648ms2026-10-10 UTC: p95 563ms2026-10-11 UTC: p95 640ms2026-10-12 UTC: p95 602ms2026-10-13 UTC: p95 574ms2026-10-14 UTC: p95 612ms2026-10-15 UTC: p95 681ms2026-10-16 UTC: p95 708ms2026-10-17 UTC: p95 999ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
UK
1.3sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 378ms2026-10-08 UTC: p95 409ms2026-10-09 UTC: p95 348ms2026-10-10 UTC: p95 348ms2026-10-11 UTC: p95 277ms2026-10-12 UTC: p95 272ms2026-10-13 UTC: p95 421ms2026-10-14 UTC: p95 308ms2026-10-15 UTC: p95 442ms2026-10-16 UTC: p95 375ms2026-10-17 UTC: p95 752ms2026-10-18 UTC: p95 870ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 799ms2026-11-01 UTC: p95 873ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Southeast Asia
2.3sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 3.1s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Australia
3.5sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 2.4s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 2.2s2026-10-15 UTC: p95 2.4s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.5s2026-10-19 UTC: p95 3.9s2026-10-20 UTC: p95 4.1s2026-10-21 UTC: p95 4.0s2026-10-22 UTC: p95 3.2s2026-10-23 UTC: p95 3.2s2026-10-24 UTC: p95 3.5s2026-10-25 UTC: p95 3.5s2026-10-26 UTC: p95 3.4s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.8s2026-10-31 UTC: p95 3.6s2026-11-01 UTC: p95 3.3s2026-11-02 UTC: p95 3.4s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5
South America
2.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 8.0s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Snapchat

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Snapchat. It cannot diagnose Snapchat's own systems.

What we measured, function by function

Snapchat answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Snap MapUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Snapchat for WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • SpotlightUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 570msstatus code: 200checked: Nov 5, 2026, 2:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Snapchat normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1208msstatus code: 200checked: Nov 5, 2026, 2:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Snapchat normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 723msstatus code: 200checked: Nov 5, 2026, 2:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Snapchat normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 766msstatus code: 200checked: Nov 5, 2026, 2:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Snapchat normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1163msstatus code: 200checked: Nov 5, 2026, 2:34 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Snapchat normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 965msstatus code: 200checked: Nov 5, 2026, 2:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Snapchat normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 189msstatus code: 200checked: Nov 5, 2026, 2:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Snapchat normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1896msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Snapchat normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1204msstatus code: 200checked: Nov 5, 2026, 2:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Snapchat normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 3024msstatus code: 200checked: Nov 5, 2026, 2:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Snapchat normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Snapchat, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Snapchat on September 22, 2026.

Recent probe events

No probe events on record yet for Snapchat.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Snapchat since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Snapchat covering any window you pick, with our check readings and Snapchat's own claim at the time, side by side.

Full check history for Snapchat: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Snapchat uptime by RealUptime's checksLive, from this page's own readings.
[![Snapchat uptime by RealUptime's checks](https://realuptime.io/outages/snapchat/badge.svg?days=30)](https://realuptime.io/outages/snapchat)
<a href="https://realuptime.io/outages/snapchat"><img src="https://realuptime.io/outages/snapchat/badge.svg?days=30" alt="Snapchat uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Snapchat down?", https://realuptime.io/outages/snapchat. The readings change with every check, so give the date you read them.

How our checks compare with Snapchat's stated SLA

At or above your target

Our checks of Snapchat failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Snapchat's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://www.snapchat.com/
secondary
https://web.snapchat.com/
secondary
https://map.snapchat.com/
secondary
https://accounts.snapchat.com/accounts/v2/login
secondary
https://www.snapchat.com/spotlight

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.snapchat.com

RealUptime is not affiliated with Snapchat; the name identifies what we checked, and nothing here speaks for Snapchat's own team. We send a single web request to Snapchat from 10 regions on our own schedule and time the response. We do not see inside Snapchat's systems, do not use an account or real transaction, and are not the same signal Snapchat's own team has access to. Treat this as one external data point, not a verdict. What we check for Snapchat is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.