ceven

Globalping

Triggers global network diagnostics from hundreds of probes to detect regional outages, maps latency spikes to specific geographic hubs, and alerts your team when connectivity drops in a target market.

Try Globalping in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Globalping integration

    • Describe the outcome and Ceven picks the right Globalping calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Globalping data, across all 5 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Globalping access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Globalping, when, and on whose behalf.
    • The agent pauses and asks when Globalping is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Globalping.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Globalping action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Globalping, and when to use it.

Create measurement
Use this when you need to trigger a network test like ping or traceroute from a specific geographic location or probe ID.
Get measurement results
Pull the detailed output and per probe status for a specific measurement ID to analyze latency or packet loss.
Check API health
Verify the current availability of the Globalping API before triggering large scale network tests.
List probes
Pull a list of all currently connected probes to identify available locations for a new measurement.
Run ping test
Use this to check basic reachability and round trip time to a host from selected global regions.
Run traceroute
Execute a traceroute to map the network path and find the exact hop causing delays or drops.
Run DNS resolve
Verify if a domain resolves to the correct IP address from different parts of the world.
Filter probes by country
Search for available probes within a specific country code to target regional network issues.
Monitor probe status
Track if specific probes are online or offline to ensure measurement reliability.
Batch create measurements
Trigger multiple network tests across different regions simultaneously for a comprehensive health check.
Get probe metadata
Pull detailed information about a specific probe including its location and network provider.
Cancel measurement
Stop a long running network test that is no longer needed to save on system resources.
GlobalPing Health Check
Tool to check API health status. Use when verifying API availability.

13 actions · scroll to see them all

Frequently asked questions

When Ceven triggers a measurement, Globalping returns a measurement ID immediately while the probes work in the background. The Ceven agent is designed to poll the Get Measurement Results endpoint at smart intervals. It waits for the probes to report back and only proceeds to the next step of your workflow once a sufficient number of results are collected. You can configure the timeout period in your workflow settings so the agent does not wait indefinitely if a probe goes offline during the test. This ensures that your alerting logic only fires when there is a complete data set to analyze.
Yes. Globalping imposes rate limits on the number of concurrent measurements and the number of probes per request to prevent network abuse. If a Ceven workflow attempts to trigger too many simultaneous tests, the Globalping API will return a rate limit error. To handle this, Ceven implements an exponential backoff strategy that queues requests and retries them automatically. For users with very high volume needs, we recommend grouping measurements into batches or using a staggered schedule in the workflow builder to stay within the API quotas and avoid dropped tests.
While you cannot always specify a precise ISP for every single probe, you can use the List Probes action to find probes that reside on specific networks or in specific cities. Once you identify the probe IDs that match the network profile you are looking for, you can pass those IDs directly into the Create Measurement call. This allows you to simulate traffic from a specific region or provider to troubleshoot peering issues. The Ceven agent can automate this by searching for probes with specific metadata before launching the actual network test.
Network probes are community run and can go offline without notice. When a probe fails to return a result, Globalping marks that specific probe as failed in the results object. Ceven parses these results and calculates a success percentage. If your workflow is set to alert on a failure, you can define a threshold, such as alerting only if more than twenty percent of probes in a region fail. This prevents false positives caused by a single unstable probe and ensures that you only get notified when there is a genuine regional outage.
Globalping focuses on the network layer, meaning it handles ping, traceroute, and DNS. It does not perform deep packet inspection or SSL handshake verification. To monitor SSL certificates, you would typically use a different tool. However, you can use Ceven to create a hybrid workflow where a separate monitoring tool detects an SSL error, and then Ceven triggers Globalping to verify if the server is even reachable via the network. This helps you quickly distinguish between a certificate configuration error and a total server crash or routing failure.
No VPN is required. The Globalping API acts as the orchestrator that sends instructions to the distributed probes. When Ceven makes an API call, it is communicating with the Globalping control plane, which then relays the request to the probes. The probes execute the test from their own local network environment and send the results back to the API. This means you get a true external view of your network performance from the perspective of a user in that region without needing to manage your own proxy or VPN infrastructure.
Globalping tests typically use standard network protocols like ICMP for ping and UDP for traceroute. These protocols do not transmit sensitive application data; they only measure the time it takes for a packet to travel to a destination and back. Since Ceven only interacts with the Globalping API over encrypted HTTPS, your API keys and measurement parameters are secure. However, be aware that traceroutes reveal the hops between the probe and your server, which means some of your internal network topology may be visible in the results if you do not have firewall rules to hide them.
Yes. While Globalping is primarily a request response tool, Ceven provides the scheduling layer. You can set up a cron job within the Ceven workflow builder to trigger a set of Globalping measurements every five minutes, hour, or day. The agent can then store these results in a database or a spreadsheet to track latency trends over time. If the latency exceeds a specific millisecond threshold that you define, the agent can automatically trigger a follow up traceroute to diagnose the cause before notifying your team via Slack or PagerDuty.

Alternatives to Globalping

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

ThousandEyes logoThousandEyesCatchpoint logoCatchpointPingdom logoPingdom

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Globalping and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free