IP addresses in Singapore
What an IP address located in Singapore carries: the registries that allocated its space and how much, the privacy regime, sanctions programmes and FATF list a lookup answers for it, the clock it keeps, and how well free geolocation places a city here. Read from the registries’ statistics and the curated facts files, never from a person.
What the registries record for Singapore
The five regional Internet registries publish daily statistics of every block they have allocated or assigned, each with the country they recorded for it. These are the rows that name Singapore as of the statistics dated 2026-09-12. A registry country is what the registrant declared, and it can differ from where an address is used.
| registries | ARIN, RIPE NCC, APNIC |
|---|---|
| ipv4 addresses | 27,828,544 in 1,891 blocks |
| ipv6 ranges | 517 |
| autonomous systems | 723 |
| allocated between | 1984 and 2026 |
| statistics dated | 2026-09-12 |
| continent | AS |
| is_eu / is_eea | false / false |
| privacy_regime | pdpa |
| sanctions | [] |
| fatf_list | null |
| calling_code | +65 |
| currency | SGD |
| timezone | Asia/Singapore |
What a lookup answers for an address here
Every IP lookup that places an address in Singapore carries the same country facts beside the network: is_eu false, is_eea false, currency SGD and calling_code 65. The three below are facts about the place from curated files that name their sources and dates; none of them is advice and none carries a risk weight.
- Privacy law. a Personal Data Protection Act: a lookup here answers privacy_regime: pdpa.
- Sanctions. No country-related US (OFAC) sanctions programme names Singapore; a lookup answers sanctions: [].
- FATF. Singapore is on neither FATF list; a lookup answers fatf_list: null.
- Clock. Asia/Singapore — the whole country keeps one clock, so every address here answers that zone.
How well free geolocation places a city in Singapore
21 of 69 compared addresses in Singapore were placed in the same city by the database and by the network operator’s own declaration: 30.4 % agreement. That is agreement between two data sources, never ground truth of a person’s location, and it is what grades location_confidence for database-located addresses here.
Measured weekly by re-locating addresses whose operators publish their own location — clouds, relays, VPN servers and RFC 8805 geofeeds — and comparing the database’s city with the declared one. Country-level agreement is far higher everywhere; city-level precision from free data is approximate and should never carry a compliance or identity decision on its own.
Run the lookup
The same fields, with the network, the operator and every flag beside them, for any address:
curl https://spaw.co/api/v1/ip \
-H "Authorization: Bearer sk_live_…" \
-H "Content-Type: application/json" \
-d '{"ip": "203.0.113.9"}'Or try one without a key on the free IP lookup, and read every field in the IP intelligence guide.
Other countries
More free tools
All free toolsNeed this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.