ProjectsOONI Coverage

OONI coverage in Singapore

On this page
  1. Networks with the most users
  2. Networks without measurements
  3. Where measurements come from
  4. Daily measurements
  5. Users covered
  6. Messaging app tests
  7. Across regions
  8. Glossary
  9. How the numbers are calculated
  10. Help fill the gaps
  11. Reading the measurement data

OONI's censorship measurements come from volunteers running OONI Probe on their own connections. Within one region, each provider and network (ASN, autonomous system number) may block different sites, so when only one or two providers are measured, blocking on the others goes unrecorded. This page sets OONI's measurement counts against APNIC's estimates of how many users each network has, to show how many users the measurements cover, which networks they concentrate on, and which networks have none.

The page is regenerated every hour and OONI's measurements are read every six hours. Taiwan is shown by default, with other regions as reference points; switch between them with the region list below. The glossary at the end of the page explains the fields. Each quarter's changes are written up in the quarterly reports.

ChinaMyanmarCambodiaPakistanBangladeshTaiwan Users covered 88.6%Hong Kong Users covered 66.6%Macau Users covered 85.9%Japan Users covered 84.4%South Korea Users covered 94.5%Vietnam Users covered 99.0%Thailand Users covered 97.5%Malaysia Users covered 96.5%Indonesia Users covered 80.6%Philippines Users covered 89.9%India Users covered 91.6%Singapore Users covered 82.1%
Users covered<75%75–85%85–90%90–95%≥95%SingaporeReference (app table only)Select a region on the map to open its page. Reference regions appear only in the messaging app table, for contrast with their records of blocking.

Measurements up to 2026-10-19 UTC · user estimates from 2026-10-15

Networks measured 54 -1vs previous 30 days
Users covered 82.1% +1.6 ppvs previous 30 days
Measurements 211,080 -45,216vs previous 30 days
Top two networks 52.1% +4.5 ppvs previous 30 days

Cards show the last 30 days, and the small charts show each day over the last 60. One measurement is OONI Probe's result for one website or service, so a single run of the website test produces hundreds. Users covered is the share of the region's internet users on networks with measurements. A lower share for the top two networks means the measurements are more spread out. pp means percentage points, the difference between two percentages.

Networks with the most users

The ten networks with the most users by the estimates of APNIC, the registry that allocates IP addresses and ASNs in the Asia Pacific. Users is the network's share of the region's internet users, Measured is its share of the region's measurements over the last 30 days, and Days is how many of those days it had any. Names are copied from registry records; in Taiwan, for example, HINET is Chunghwa Telecom's fixed network and EMOME-NET its mobile network. Networks with many users and few measurements are where running OONI Probe helps most.

Networks with the most usersUsersMeasured
ASNNameUsersMeasuredDays
AS9506 AS9506SINGTEL-FIBRE - Singtel Fibre Broadband 15.5% 12.8% 30
AS55430 AS55430STARHUB-NGNBN - Starhub Ltd 11.7% 1.3% 10
AS45143 AS45143SINGTELMOBILE-AS-AP - SINGTEL MOBILE INTERNET SERVICE PROVIDER Singapore 8.0% 0.6% 16
AS4773 AS4773MOBILEONELTD-AS-AP - MobileOne Ltd. Mobile/Internet Service Provider Singapore 7.6% 0.1% 5
AS4817 AS4817STPL-SG-AP - Simba Telecom Pte Ltd 4.8% <0.1% 1
AS16509 AS16509AMAZON-02 - Amazon.com, Inc. 4.7% 8.4% 26
AS30058 AS30058FDCSERVERS - FDCservers.net 4.4% <0.1% 1
AS62610 AS62610ZEN-DPS - Zenlayer Inc 4.3% <0.1% 1
AS4657 AS4657STARHUB-INTERNET - StarHub Ltd 3.9% 0.9% 15
AS13335 AS13335CLOUDFLARENET - Cloudflare, Inc. 2.3% 0.0% 0

Networks without measurements

32 networks with at least 0.1% of users had no measurements in the last 30 days, about 13.3% of users in total.

ASNNameUsers
AS13335 AS13335CLOUDFLARENET - Cloudflare, Inc. 2.32%
AS31898 AS31898ORACLE-BMC-31898 - Oracle Corporation 0.78%
AS135600 AS135600WHIZCOMMS-AS-AP - Whiz Communications Pte Ltd 0.74%
AS60068 AS60068CDN77 - Datacamp Limited 0.74%
AS48266 AS48266Catixs - Catixs Ltd 0.73%
AS51847 AS51847NEAROUTE - Nearoute Limited 0.73%
AS152194 AS152194CTGSERVERLIMITED-AS-AP - CTG Server Limited 0.68%
AS53813 AS53813ZSCALER-INC - ZSCALER, INC. 0.66%

Where measurements come from

Each network's share of measurements over the last 30 days. When a few networks account for most of them, the rest can only be judged from scattered data.

Measurements by networkAS53724AS56300AS9506AS16509AS395092Others
  • AS53724EVM - EXTRAVM LLC36.1%
  • AS56300MYREPUBLIC-SG - MyRepublic Ltd.15.9%
  • AS9506SINGTEL-FIBRE - Singtel Fibre Broadband12.8%
  • AS16509AMAZON-02 - Amazon.com, Inc.8.4%
  • AS395092SHOCK-1 - Shock Hosting LLC8.1%
  • Others18.7%

13 more networks are not in APNIC's user estimates and account for 40.0% of measurements; most are academic, hosting, or cloud networks.

Daily measurements

Measurements OONI Probe sends from this region each day, split by result. OK means the result matched the control. An anomaly means it did not, which can be blocking but also an unstable connection or a problem with the site itself. Confirmed blocking is an anomaly that matches a known blocking pattern, such as a redirect to a block page. Failure means the test did not complete, for example because the connection dropped midway.

Measurements per dayOKAnomalyConfirmedFailure
010k20k08/2109/2010/192026/08/21 OK 8,0912026/08/21 Anomaly 1532026/08/21 Confirmed 02026/08/21 Failure 2092026/08/22 OK 7,3422026/08/22 Anomaly 672026/08/22 Confirmed 02026/08/22 Failure 1572026/08/23 OK 11,0032026/08/23 Anomaly 2002026/08/23 Confirmed 02026/08/23 Failure 1982026/08/24 OK 8,6412026/08/24 Anomaly 1002026/08/24 Confirmed 02026/08/24 Failure 1982026/08/25 OK 10,9072026/08/25 Anomaly 2122026/08/25 Confirmed 02026/08/25 Failure 1,6572026/08/26 OK 8,7422026/08/26 Anomaly 1232026/08/26 Confirmed 32026/08/26 Failure 1352026/08/27 OK 7,8602026/08/27 Anomaly 1442026/08/27 Confirmed 02026/08/27 Failure 2292026/08/28 OK 8,6422026/08/28 Anomaly 1902026/08/28 Confirmed 02026/08/28 Failure 2422026/08/29 OK 9,9182026/08/29 Anomaly 1732026/08/29 Confirmed 02026/08/29 Failure 2972026/08/30 OK 9,6632026/08/30 Anomaly 1382026/08/30 Confirmed 02026/08/30 Failure 2442026/08/31 OK 7,8642026/08/31 Anomaly 3242026/08/31 Confirmed 02026/08/31 Failure 2552026/09/01 OK 6,7592026/09/01 Anomaly 1732026/09/01 Confirmed 02026/09/01 Failure 2182026/09/02 OK 7,0792026/09/02 Anomaly 1722026/09/02 Confirmed 02026/09/02 Failure 2002026/09/03 OK 5,3382026/09/03 Anomaly 2012026/09/03 Confirmed 02026/09/03 Failure 1882026/09/04 OK 6,7072026/09/04 Anomaly 1592026/09/04 Confirmed 02026/09/04 Failure 2002026/09/05 OK 6,2232026/09/05 Anomaly 1382026/09/05 Confirmed 02026/09/05 Failure 1412026/09/06 OK 5,5702026/09/06 Anomaly 1622026/09/06 Confirmed 02026/09/06 Failure 1852026/09/07 OK 5,2762026/09/07 Anomaly 1442026/09/07 Confirmed 02026/09/07 Failure 1212026/09/08 OK 6,0872026/09/08 Anomaly 1372026/09/08 Confirmed 02026/09/08 Failure 1762026/09/09 OK 8,8392026/09/09 Anomaly 1292026/09/09 Confirmed 02026/09/09 Failure 2282026/09/10 OK 9,1632026/09/10 Anomaly 2132026/09/10 Confirmed 02026/09/10 Failure 4322026/09/11 OK 10,9362026/09/11 Anomaly 3362026/09/11 Confirmed 02026/09/11 Failure 6962026/09/12 OK 8,5432026/09/12 Anomaly 1282026/09/12 Confirmed 02026/09/12 Failure 2852026/09/13 OK 7,5432026/09/13 Anomaly 1522026/09/13 Confirmed 02026/09/13 Failure 2452026/09/14 OK 7,6892026/09/14 Anomaly 1152026/09/14 Confirmed 02026/09/14 Failure 1432026/09/15 OK 6,3132026/09/15 Anomaly 1142026/09/15 Confirmed 02026/09/15 Failure 2342026/09/16 OK 5,6392026/09/16 Anomaly 1022026/09/16 Confirmed 02026/09/16 Failure 892026/09/17 OK 9,8492026/09/17 Anomaly 1252026/09/17 Confirmed 02026/09/17 Failure 1822026/09/18 OK 11,0372026/09/18 Anomaly 1982026/09/18 Confirmed 02026/09/18 Failure 1992026/09/19 OK 9,9882026/09/19 Anomaly 1782026/09/19 Confirmed 02026/09/19 Failure 1592026/09/20 OK 9,3532026/09/20 Anomaly 1592026/09/20 Confirmed 12026/09/20 Failure 2612026/09/21 OK 11,4022026/09/21 Anomaly 2002026/09/21 Confirmed 12026/09/21 Failure 3072026/09/22 OK 8,9242026/09/22 Anomaly 2152026/09/22 Confirmed 02026/09/22 Failure 2152026/09/23 OK 8,4022026/09/23 Anomaly 1662026/09/23 Confirmed 02026/09/23 Failure 1992026/09/24 OK 5,8792026/09/24 Anomaly 1762026/09/24 Confirmed 02026/09/24 Failure 1402026/09/25 OK 5,8792026/09/25 Anomaly 1782026/09/25 Confirmed 02026/09/25 Failure 1352026/09/26 OK 5,7692026/09/26 Anomaly 1292026/09/26 Confirmed 02026/09/26 Failure 972026/09/27 OK 4,8812026/09/27 Anomaly 1042026/09/27 Confirmed 02026/09/27 Failure 2672026/09/28 OK 5,0732026/09/28 Anomaly 1492026/09/28 Confirmed 02026/09/28 Failure 1242026/09/29 OK 5,7902026/09/29 Anomaly 1262026/09/29 Confirmed 02026/09/29 Failure 1712026/09/30 OK 5,2382026/09/30 Anomaly 1032026/09/30 Confirmed 02026/09/30 Failure 912026/10/01 OK 5,1782026/10/01 Anomaly 1642026/10/01 Confirmed 02026/10/01 Failure 1932026/10/02 OK 4,5612026/10/02 Anomaly 902026/10/02 Confirmed 02026/10/02 Failure 1002026/10/03 OK 5,0552026/10/03 Anomaly 872026/10/03 Confirmed 02026/10/03 Failure 872026/10/04 OK 5,1862026/10/04 Anomaly 1202026/10/04 Confirmed 02026/10/04 Failure 1662026/10/05 OK 5,0242026/10/05 Anomaly 1092026/10/05 Confirmed 02026/10/05 Failure 1552026/10/06 OK 6,8052026/10/06 Anomaly 1342026/10/06 Confirmed 02026/10/06 Failure 2682026/10/07 OK 6,6592026/10/07 Anomaly 1412026/10/07 Confirmed 02026/10/07 Failure 4262026/10/08 OK 5,4192026/10/08 Anomaly 1362026/10/08 Confirmed 02026/10/08 Failure 2722026/10/09 OK 5,0312026/10/09 Anomaly 1252026/10/09 Confirmed 02026/10/09 Failure 2402026/10/10 OK 4,8412026/10/10 Anomaly 1142026/10/10 Confirmed 02026/10/10 Failure 3062026/10/11 OK 4,1802026/10/11 Anomaly 962026/10/11 Confirmed 02026/10/11 Failure 862026/10/12 OK 5,1342026/10/12 Anomaly 1312026/10/12 Confirmed 02026/10/12 Failure 3332026/10/13 OK 6,0832026/10/13 Anomaly 2052026/10/13 Confirmed 02026/10/13 Failure 4262026/10/14 OK 6,2982026/10/14 Anomaly 1982026/10/14 Confirmed 22026/10/14 Failure 3482026/10/15 OK 8,9862026/10/15 Anomaly 5332026/10/15 Confirmed 402026/10/15 Failure 4522026/10/16 OK 10,6262026/10/16 Anomaly 8672026/10/16 Confirmed 322026/10/16 Failure 6362026/10/17 OK 8,7812026/10/17 Anomaly 2352026/10/17 Confirmed 872026/10/17 Failure 5582026/10/18 OK 7,9922026/10/18 Anomaly 3282026/10/18 Confirmed 292026/10/18 Failure 4582026/10/19 OK 8,8072026/10/19 Anomaly 2422026/10/19 Confirmed 542026/10/19 Failure 321
Networks measured per day
0102008/2109/2010/192026/08/21 Networks measured 102026/08/22 Networks measured 82026/08/23 Networks measured 152026/08/24 Networks measured 132026/08/25 Networks measured 192026/08/26 Networks measured 92026/08/27 Networks measured 72026/08/28 Networks measured 142026/08/29 Networks measured 122026/08/30 Networks measured 92026/08/31 Networks measured 102026/09/01 Networks measured 132026/09/02 Networks measured 132026/09/03 Networks measured 162026/09/04 Networks measured 92026/09/05 Networks measured 112026/09/06 Networks measured 82026/09/07 Networks measured 82026/09/08 Networks measured 82026/09/09 Networks measured 92026/09/10 Networks measured 142026/09/11 Networks measured 122026/09/12 Networks measured 92026/09/13 Networks measured 122026/09/14 Networks measured 112026/09/15 Networks measured 102026/09/16 Networks measured 102026/09/17 Networks measured 102026/09/18 Networks measured 132026/09/19 Networks measured 132026/09/20 Networks measured 112026/09/21 Networks measured 102026/09/22 Networks measured 102026/09/23 Networks measured 142026/09/24 Networks measured 102026/09/25 Networks measured 92026/09/26 Networks measured 92026/09/27 Networks measured 92026/09/28 Networks measured 102026/09/29 Networks measured 122026/09/30 Networks measured 102026/10/01 Networks measured 92026/10/02 Networks measured 92026/10/03 Networks measured 72026/10/04 Networks measured 82026/10/05 Networks measured 122026/10/06 Networks measured 112026/10/07 Networks measured 92026/10/08 Networks measured 132026/10/09 Networks measured 82026/10/10 Networks measured 62026/10/11 Networks measured 122026/10/12 Networks measured 82026/10/13 Networks measured 102026/10/14 Networks measured 132026/10/15 Networks measured 112026/10/16 Networks measured 152026/10/17 Networks measured 122026/10/18 Networks measured 102026/10/19 Networks measured 8

Users covered

The share of this region's internet users, by APNIC's estimates, on networks that had at least one measurement that day. One measurement is enough to count, so this is an upper bound rather than a sign that every network is measured enough.

Users covered (%)
05010008/2109/2010/192026/08/21 Users covered 23.12026/08/22 Users covered 26.42026/08/23 Users covered 39.82026/08/24 Users covered 29.62026/08/25 Users covered 32.72026/08/26 Users covered 26.52026/08/27 Users covered 21.72026/08/28 Users covered 46.32026/08/29 Users covered 28.12026/08/30 Users covered 26.52026/08/31 Users covered 30.52026/09/01 Users covered 36.82026/09/02 Users covered 40.92026/09/03 Users covered 38.92026/09/04 Users covered 23.12026/09/05 Users covered 23.62026/09/06 Users covered 26.72026/09/07 Users covered 28.02026/09/08 Users covered 39.32026/09/09 Users covered 27.02026/09/10 Users covered 35.22026/09/11 Users covered 34.72026/09/12 Users covered 27.02026/09/13 Users covered 28.72026/09/14 Users covered 37.92026/09/15 Users covered 43.22026/09/16 Users covered 38.42026/09/17 Users covered 37.62026/09/18 Users covered 35.02026/09/19 Users covered 35.72026/09/20 Users covered 37.32026/09/21 Users covered 44.32026/09/22 Users covered 29.02026/09/23 Users covered 47.22026/09/24 Users covered 29.52026/09/25 Users covered 36.82026/09/26 Users covered 38.12026/09/27 Users covered 50.42026/09/28 Users covered 56.92026/09/29 Users covered 49.42026/09/30 Users covered 43.92026/10/01 Users covered 43.12026/10/02 Users covered 35.12026/10/03 Users covered 43.12026/10/04 Users covered 32.62026/10/05 Users covered 29.32026/10/06 Users covered 36.52026/10/07 Users covered 24.22026/10/08 Users covered 31.02026/10/09 Users covered 23.42026/10/10 Users covered 22.42026/10/11 Users covered 33.22026/10/12 Users covered 30.42026/10/13 Users covered 34.22026/10/14 Users covered 50.12026/10/15 Users covered 24.82026/10/16 Users covered 31.62026/10/17 Users covered 28.12026/10/18 Users covered 32.92026/10/19 Users covered 28.2

Steady coverage

Coverage counts a network as soon as it has a single measurement, even if it was measured on only a day or two. Steady coverage counts only networks measured on at least 15 of the last 30 days. The wider the gap between the two, the more users sit on networks with only scattered measurements.

Users covered 82.1% Measured on at least one day
Users steadily covered 35.2% Measured on at least 15 days

Messaging app tests

OONI Probe tests whether the servers of Signal, WhatsApp and Telegram can be reached. An anomaly only means the result differed from what was expected, which an unstable connection can also cause. An anomaly rate close to 100% usually means the app is blocked there. Rates are left out when there were fewer than 30 measurements in the last 30 days.

Anomaly rate in Singapore, last 30 days
  • Signal1.0%
  • WhatsApp0.3%
  • Telegram1.2%

Up to 1,195 measurements per app

Across regions

Users covered by networks measured in the last 30 days. Each small chart shows the daily coverage over the last 60 days on one shared scale, so the levels compare directly. Open a region for its full charts.

Small-chart scale: 0% to 100%.

RegionCoveredSteady
TaiwanTW 88.6% 54.1%
Hong KongHK 66.6% 31.2%
MacauMO 85.9% 0.0%
JapanJP 84.4% 72.9%
South KoreaKR 94.5% 81.8%
SingaporeSG 82.1% 35.2%
VietnamVN 99.0% 93.9%
ThailandTH 97.5% 48.9%
MalaysiaMY 96.5% 95.1%
IndonesiaID 80.6% 69.7%
PhilippinesPH 89.9% 86.9%
IndiaIN 91.6% 86.3%

Messaging app anomaly rates across regions

Anomaly rates over the last 30 days, with rates above half highlighted. The last rows are reference regions without their own pages, which have records of blocking to compare against.

RegionSignalWhatsAppTelegram
TaiwanTW 0.9%1.8%1.6%
Hong KongHK 1.0%0.7%0.5%
MacauMO –––
JapanJP 0.5%0.7%0.5%
South KoreaKR 0.2%2.7%2.4%
SingaporeSG 1.0%0.3%1.2%
VietnamVN 0.1%0.2%0.5%
ThailandTH 0.5%0.2%0.3%
MalaysiaMY <0.1%0.1%1.1%
IndonesiaID 3.0%0.5%0.7%
PhilippinesPH 0.2%0.1%2.6%
IndiaIN 1.9%0.4%1.7%
Reference regions
ChinaCN 98.6%98.2%99.1%
MyanmarMM 97.3%98.8%0.4%
CambodiaKH 29.6%35.4%2.4%
PakistanPK 97.2%0.6%99.4%
BangladeshBD 0.5%0.2%0.3%

Glossary

  • OONI Probe: an open-source app from OONI that tests from a phone or computer whether websites and services can be reached, with the results published in OONI's database
  • Measurement: one result of OONI Probe testing one website or service. A single run of the website test produces hundreds, so a high count does not mean many people ran tests
  • Autonomous system (ASN): a group of networks run by one organisation under one routing policy, such as a telecom, a university or a cloud provider, each with its own AS number. A telecom's fixed and mobile networks are often separate ASNs
  • Network names: copied from APNIC and RIPE NCC registry records and often abbreviated. In Taiwan, for example, HINET is Chunghwa Telecom's fixed network and EMOME-NET its mobile network
  • APNIC: the Asia Pacific Network Information Centre, which allocates IP addresses and ASNs in the region and estimates each network's users from sampled web ads
  • Users, Measured (%): Users is the network's share of the region's internet users, and Measured is its share of the region's measurements. The further apart the two are, the more the measurements are out of proportion to the users
  • Days: how many of the last 30 days had any measurements
  • Users covered: the share of the region's internet users on networks with measurements, where a single measurement is enough to count
  • Users steadily covered: counts only networks measured on at least 15 of the last 30 days
  • Top two networks: the share of measurements from the two most measured networks; lower means more spread out
  • pp (percentage points): the difference between two percentages. Coverage going from 94.6% to 93.9% is written as −0.7 pp
  • OK, anomaly, confirmed, failure: OK means the result matched the control. An anomaly means it did not, which can be blocking or an unstable connection. Confirmed blocking is an anomaly matching a known blocking pattern. A failure is a test that did not complete
  • Anomaly rate (messaging apps): the share of the app's measurements that were anomalies. Close to 100% usually means the app is blocked there
  • Reference region: a region without its own page, listed in a comparison table for contrast

How the numbers are calculated

  • Measurement counts come from OONI's aggregation API, across all tests, grouped by the day each measurement started (UTC)
  • Users per network are APNIC's estimates, derived from ad-based sampling and updated weekly
  • Network names come from the APNIC and RIPE NCC ASN name lists
  • A single measurement is enough for a network to count as measured; whether it is measured enough shows in its share of measurements and the number of days
  • Steady coverage counts only networks measured on at least 15 of the last 30 days
  • Messaging app results also come from the OONI aggregation API, counted by region; the reference regions at the end of the table have no pages of their own
  • Days without measurements are left as gaps in the charts rather than filled in

Help fill the gaps

  • Install OONI Probe and run tests on your own connection, on a phone or a computer. Mobile data and home broadband are usually different ASNs, so testing on both helps
  • The community's OONI Run link 10328 sets everything up in one tap; see the OONI Run v2 guide for the risks to consider before installing and what the list contains
  • Maintaining the OONI Test List: the list decides which websites get tested, and help with Taiwan's tw.csv is welcome
  • ASN Coverage: a command-line tool that downloads raw measurements and breaks them down by network type and blocking method

Reading the measurement data