BigDataCloud

A status report for the whole IPv4 address space: total, announced and bogon address counts with the registry allocation breakdown, combining registry data (refreshed at least daily) with live BGP state (every two hours). Takes no arguments. Reached over GET https://api-bdc.net/data/address-space-stats-ipv4 in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The IPv6 counterpart of `bigdatacloud_get_address_space_stats_ipv4`: total, announced and bogon counts over the 2^128 IPv6 space with the registry breakdown. Takes no arguments. BigDataCloud publishes no REST reference page for this endpoint -- it is documented as the `ipV6` field of the network-engineering GraphQL schema and was confirmed live on 2026-09-24 UTC (200 with the key, 403 without). Reached over GET https://api-bdc.net/data/address-space-stats-ipv6 in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Registration details, announced IPv4 address space and global rank for one autonomous system. The short form; `bigdatacloud_get_asn_info_full` adds routing relationships. An ASN that does not exist answers 404 'no valid entry found for the request'. Reached over GET https://api-bdc.net/data/asn-info in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Everything `bigdatacloud_get_asn_info` returns plus the networks this autonomous system receives traffic from and transits traffic to, and the coordinates of its most active operating region. The routing data is refreshed every two hours. `peersCap` caps each relationship list at 50; page beyond that with `bigdatacloud_get_asn_info_receiving_from` and `bigdatacloud_get_asn_info_transit_to`. THIS RESPONSE IS LARGE -- AS15169 returns about 115 KB. Reached over GET https://api-bdc.net/data/asn-info-full in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The upstream and peering side of one autonomous system's routing relationships, paginated. Use this rather than `bigdatacloud_get_asn_info_full` when the list is long: 50 is the hard batch limit, and `offset` walks the rest. Reached over GET https://api-bdc.net/data/asn-info-receiving-from in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The downstream side of one autonomous system's routing relationships, paginated. The companion to `bigdatacloud_get_asn_info_receiving_from`; 50 is the hard batch limit. Reached over GET https://api-bdc.net/data/asn-info-transit-to in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Every autonomous system BigDataCloud tracks, ranked by the total IPv4 address count it announces on BGP -- about 81,000 of them -- sortable and paginated. Takes no required argument: it is the whole list. `total` in the response is the population, not the page. Reached over GET https://api-bdc.net/data/asn-rank-list in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Country-level context for an address -- ISO names and codes, official languages, currency, calling code, UN region and World Bank income level -- without the full geolocation payload. The lightweight choice for form localisation, currency selection or regional content. Reached over GET https://api-bdc.net/data/country-by-ip in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Reference data for a country given its ISO 3166-1 code: isoAlpha-2, isoAlpha-3 and M49 numeric codes, ISO names, official languages, currency, calling code, flag emoji, UN region and World Bank income level. Takes a COUNTRY CODE, not an IP address. An unknown code answers 404 'no valid entry found for the request'. Reached over GET https://api-bdc.net/data/country-info in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Check one address before it reaches your database: full RFC 822 / 2822 / 5321 syntax compliance, whether the domain has a working mail server, and whether it belongs to a known disposable or abusive domain. NO SMTP HANDSHAKE IS PERFORMED, so nothing is delivered and no receiving server sees a probe -- which also means a syntactically valid address on a live domain can still be an empty mailbox. Reached over GET https://api-bdc.net/data/email-verify in BigDataCloud's Phone & Email Verification package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The risk signals for one address on their own: Tor, VPN and proxy flags, Spamhaus DROP/EDROP/ASN-DROP and other blocklist appearances, mail-server and public-router flags, bogon and unreachable flags, cellular and iCloud Private Relay flags, and `hostingLikelihood` (0-10, how likely the address is data-centre rather than residential). The same object is embedded in `bigdatacloud_get_ip_geolocation_full`. Reached over GET https://api-bdc.net/data/hazard-report in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Geolocate an IPv4 or IPv6 address to country, region, city and locality, with the network and time zone that serve it. BigDataCloud locates an address by identifying the router that delivers traffic to it and that router's measured service area (US Patent 11,792,110 B2) rather than by reading a WHOIS registration, so the answer describes how the network actually routes. Reached over GET https://api-bdc.net/data/ip-geolocation in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The widest IP answer BigDataCloud gives: geolocation, the confidence-area polygon and the hazard report in one call. The hazard report adds forward-looking risk signal -- whether the address belongs to hosting infrastructure rather than a residential network (`hostingLikelihood`, 0-10) -- to the backward-looking blocklist and anonymiser flags. Prefer this over three separate calls: BigDataCloud meters by call, so one wide call costs less quota than the parts. Reached over GET https://api-bdc.net/data/ip-geolocation-full in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Everything `bigdatacloud_get_ip_geolocation` returns, plus a `confidenceArea` polygon: the other places this address may be found when it is assigned dynamically or shared. THE POLYGON IS AN ESTIMATE, NOT A BOUNDARY -- its size is not a confidence score and it says nothing about how the address is distributed inside it. Read `country` first, then `confidenceArea`, then the `location` pin. Reached over GET https://api-bdc.net/data/ip-geolocation-with-confidence in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The sub-prefixes actually announced on BGP inside a CIDR block, with their autonomous systems and registration details. `depthLimit` controls how far down the sub-prefix nesting is walked, and `subnetsBatchSize`/`subnetsOffset` page the subnet list (20 is both the default and the hard limit). Reached over GET https://api-bdc.net/data/network-by-cidr in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Network-level context rather than a location: the registry and registration status, the BGP prefix, the organisation, and the autonomous systems that announce (`carriers`) and transit (`viaCarriers`) the address, each with its rank. Reached over GET https://api-bdc.net/data/network-by-ip in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Normalise and validate a phone number against E.164: returns the E.164, international and national spellings, the line type (mobile, fixed line, VoIP, toll free and so on) and country context. `countryCode` tells it which national format to read a local number in; a number already in +E.164 form does not need one. Reached over GET https://api-bdc.net/data/phone-number-validate in BigDataCloud's Phone & Email Verification package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The same validation as `bigdatacloud_get_phone_number_validate`, but the expected country is inferred from an IP address instead of being passed as a code -- for sign-up forms with no country selector. PASS THE END USER'S ADDRESS EXPLICITLY: omitting `ip` makes the provider use the caller's, which here is the gateway's own egress address, and a national-format number is then read against the wrong country (measured 2026-09-24 UTC: a US number came back as +92, Pakistan). Reached over GET https://api-bdc.net/data/phone-number-validate-by-ip in BigDataCloud's Phone & Email Verification package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The prefixes currently announced on BGP, paginated -- over 1.5 million of them unfiltered. Narrow with `asn` to one autonomous system, or with `bogonsOnly=true` to reserved or unallocated space that should not be routed at all. `isv4=false` returns IPv6 prefixes; IPv4 is assumed when the flag is omitted. Reached over GET https://api-bdc.net/data/prefixes-list in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Turn latitude and longitude into structured locality data: continent, country, principal subdivision, city, locality and postcode, with the administrative hierarchy behind them. BigDataCloud resolves to administrative and non-administrative BOUNDARIES rather than to the nearest street address, so the answer stays consistent where street data is sparse. This is the SERVER-SIDE, keyed endpoint -- the free client-side one is not shipped here. Reached over GET https://api-bdc.net/data/reverse-geocode in BigDataCloud's Reverse Geocoding package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

`bigdatacloud_get_reverse_geocode` and `bigdatacloud_get_timezone_by_location` in one call. Prefer it when you need both: BigDataCloud meters by call, so this is half the quota and half the latency of asking twice. Reached over GET https://api-bdc.net/data/reverse-geocode-with-timezone in BigDataCloud's Reverse Geocoding package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The IANA time zone for an address -- identifier, display name, UTC offset, daylight-saving state and current local time -- resolved from the address, so no separate geolocation call is needed. Reached over GET https://api-bdc.net/data/timezone-by-ip in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The IANA time zone for a pair of coordinates -- identifier, UTC offset, daylight-saving state and schedule, and local time. Pass `utcReference` to convert a specific instant rather than now. Reached over GET https://api-bdc.net/data/timezone-by-location in BigDataCloud's Reverse Geocoding package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Current details for an IANA time zone you already know the name of: UTC offset, daylight-saving state and schedule, and local time. Pass `utcReference` to convert a specific instant instead of now. Takes a ZONE ID, not coordinates or an address; an unrecognised id answers 400 'bad request'. Reached over GET https://api-bdc.net/data/timezone-info in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

The currently active Tor exit nodes -- the addresses a destination server sees -- each geolocated to country level with its carrier. Paginated; takes no required argument. Being on this list means traffic arrived through Tor, which is not by itself evidence of anything about a person. Reached over GET https://api-bdc.net/data/tor-exit-nodes-list in BigDataCloud's Network Engineering package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

Turn a raw user-agent string into structured fields: device, operating system, browser family and version, and `isSpider` for bot and crawler detection. Pass the string you received; nothing is read from this request's own headers. Reached over GET https://api-bdc.net/data/user-agent-info in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.

One word instead of a report: `risk` is `Low`, `Moderate` or `High` for the address, with a short description. Intended as a captcha decision -- low risk looks like ordinary residential or mobile traffic. It is a heuristic about the ADDRESS, never about a person, and it is not evidence of wrongdoing; call `bigdatacloud_get_hazard_report` when you need the signals the verdict was formed from. Reached over GET https://api-bdc.net/data/user-risk in BigDataCloud's IP Geolocation package. QUOTA IS MONTHLY, NOT PER SECOND: BigDataCloud publishes no per-second or per-minute rate limit, and every plan reaches every endpoint -- you pay for volume, not for access -- so a refusal is never 'this tool needs a bigger plan', and waiting does not clear an exhausted monthly allowance. READ THE BODY, NOT THE STATUS, BECAUSE NOTHING HERE ANSWERS 401 (measured 2026-09-24 UTC, against BigDataCloud's own documentation, which promises one): a key that is refused, absent or empty all answer 403 {"status":403,"description":"access denied or your quota limit has been exceeded"} -- and an exhausted monthly allowance answers the same status with the same sentence, so 403 alone does not say which of the two happened. 400 'bad request' is what a missing required argument produces, and 404 'no valid entry found for the request' means the argument was well-formed but matched no record, such as an unknown ASN or country code.