Skip to content
Go to dashboard

7.12Browser runs and your plan

Plans that include browser monitors#

Browser monitors need a plan that includes them. If yours does not, the browser tab says "browser checks aren't part of the <plan> plan". You can select unlock with <plan>, or use a URL check instead.

Through the API, the save fails with failed_precondition and the message plan does not allow this monitor type: browser monitors require Pro or Business.

How many browser monitors you can have#

  • Your plan may limit the number of browser monitors. The browser tab then shows a meter: <used> of <limit> browser monitors used.
  • From 80% of the limit, a banner warns you. At the limit, new browser monitors can't be created until you upgrade or delete one.
  • Through the API, the save then fails with per-type monitor quota exceeded: <used>/<limit> browser monitors used on the current plan.

Browser runs#

  • Each browser check is one browser run. One run is one check from one region.
  • A monitor that checks from two regions uses two runs each time. run once now also uses a run.
  • Your plan includes a number of browser runs in each billing period. When you go over, your monitors keep running. Extra runs are billed per 1,000 runs.
  • A banner tells you when you near or pass the included runs, and shows the price per 1,000 extra runs.

To see your limits and usage, select billing in the top navigation, then the plans tab. Look for the rows browser checks, browser monitors and browser runs incl. Your usage so far is under browser runs this period.

Through the API, GetPlanLimitUsage returns PLAN_LIMIT_BROWSER_MONITORS and PLAN_LIMIT_BROWSER_RUNS (see 13.8). Each has used, limit and level. The level is PLAN_LIMIT_LEVEL_NEARING from 80% and PLAN_LIMIT_LEVEL_REACHED at 100%. For runs, overageCentsPer1k is the price of 1,000 extra runs, in cents.

Last updated