Why Hotel Wi-Fi Suddenly Triggered an Age-Verification Page

The page worked on mobile data.

The moment I joined the hotel Wi-Fi, it asked for my face.

I had arrived in London late, dropped my bag beside the bed and opened a mature-tagged discussion I had saved earlier. It was legal, public and not important enough to justify photographing my passport. Yet the site now offered facial age estimation or an identity-document check before it would let me continue.

I blamed the browser. I closed the tab, cleared the site data and tried again.

The same page returned.

Then I switched off Wi-Fi. On roaming mobile data, the discussion opened normally.

Back on the hotel network, the age check reappeared.

My account had not changed in the thirty seconds between attempts. The network had.

The Hotel Changed the Country the Site Saw

Since 25 July 2025, UK services carrying pornography and certain other material considered harmful to children have had to use stronger age checks. The rollout has extended beyond dedicated adult sites to social platforms and other services carrying restricted content. (Ofcom)

A website cannot see the hotel room around a visitor. It usually begins with the public internet address through which the connection arrives.

My roaming traffic was still exiting through infrastructure associated with my mobile provider. The hotel Wi-Fi used a local British connection. As soon as I joined it, the site saw a UK address and applied its UK verification flow.

The hotel had not decided that I needed to prove my age. It had simply introduced me to the site as a British visitor.

That small distinction explained the abrupt change. Travellers have described the same split: a page behaves normally over roaming data, then changes the moment the phone joins a hotel network. (Reddit)

Once I understood that, clearing cookies again made no sense. The site was reacting to the route in front of it. I needed to change that route.

The Hotel Login Came Before the VPN

I opened the large VPN service already installed on my phone and tapped Connect.

Nothing happened.

The Wi-Fi icon was visible, but the hotel had not fully opened the internet connection. I still needed to complete its captive portal—the sign-in page asking for my room number and surname.

Hotel and airport networks commonly hold back ordinary internet traffic until that page is completed. A VPN may appear to be connecting while the network is still waiting for its own login. (Cloudflare)

So I switched the VPN off, opened the hotel page and entered the room details. A confirmation screen told me I was online.

Without thinking, I returned to the saved discussion.

The site saw the hotel’s UK address and produced the age-verification page again.

I turned the VPN on, chose a server outside the UK and refreshed the existing tab.

The prompt remained.

That initially looked like another failure, but the tab had already entered the verification flow through the hotel connection. Changing the route did not automatically rewind the visit.

I closed it and opened a private window.

The age screen disappeared.

Then a CAPTCHA replaced it.

The Familiar Provider Removed One Gate and Added Another

I completed the CAPTCHA and received a second challenge. The next attempt loaded the page frame but not the discussion.

Then the hotel Wi-Fi dipped.

The VPN disconnected, and the browser returned to the UK age-check page.

I reconnected, selected another server and started again. The sequence repeated: connect, challenge, partial page, Wi-Fi interruption, reconnect.

The provider had a long public history and a large server network. At home, it had worked well. Here, every brief hotel-network drop broke the route and pushed the next request back toward the hotel connection.

I could not observe the site’s internal filtering rules, so I could not know whether its challenges were caused by the exit address, shared traffic or another signal. The visible problem was enough: I could not keep one accepted route alive long enough to finish loading the page.

That changed the comparison.

At first, I had been choosing countries. Now the flag in the server menu felt almost irrelevant. Any foreign route might remove the regional age gate for a moment. What mattered was whether the connection could survive the hotel Wi-Fi long enough to complete the task.

On this network, recovery mattered more than server count.

The Smaller App Stayed With the Session

I disconnected the first provider and opened OnlydogVPN.

The app did not begin with a long map or ask me to guess which country might work. I selected the preset for reaching a restricted page and connected.

Then I opened a fresh private window rather than returning to the tab the hotel network had already redirected.

The discussion loaded.

There was no age-verification screen. No camera handoff. No document request. No CAPTCHA waiting behind the missing gate.

The post appeared, the comments expanded and the linked article opened in another tab.

A few seconds later, the hotel Wi-Fi weakened again.

The page paused briefly, then continued.

That was the result I had been missing. The service uses HTTP/3-based transport with traffic obfuscation and is designed to recover when the underlying connection becomes weak or changes. The explanation mattered because it matched what happened on the screen: instead of dropping me back onto the hotel route, the session recovered and kept loading.

I did not have to choose another country, reopen the VPN app or restart the browser. More importantly, the age-verification flow did not return.

The original task was complete before the hotel network could turn it into another troubleshooting exercise.

Why the First Page Kept Returning

The hotel Wi-Fi had created two connected problems.

Its British public address triggered the UK age check. Its captive portal and unstable connection then made it difficult to establish and preserve a different route.

The order of events made the problem worse. I opened the page through the hotel connection, entered the verification flow, and only afterward tried to change routes inside the same tab.

Starting again changed that.

I completed the hotel login first. I connected the VPN before reopening the site. I used a clean browser session. Then I stayed on a route that recovered when the Wi-Fi weakened.

The established provider briefly changed the country but repeatedly lost the session. The smaller app removed the regional trigger and stayed with the page through the next interruption.

That was a more useful result than seeing a foreign IP address for a few seconds.

The Laptop Did Not Add Another Login Problem

Once the article was open on my phone, I wanted to read it on the laptop beside the bed.

With the first provider, that would have meant finding my password, signing into another account and repeating the server choices that had already failed.

The smaller service let me connect the laptop with a verification code instead.

A minute later, the same article was open on the larger screen. There was no new email-and-password login and no return to the hotel-created age check.

That was a secondary benefit, but it fitted the situation. The hotel already wanted a room number and captive-portal login from each device. The VPN did not add another conventional account routine on top.

The service has fewer server locations and a shorter public history than the large provider. But neither a wider map nor a longer company history would have kept that page open when the hotel Wi-Fi dropped.

I needed one route that could recover, not dozens I could manually reconnect to.

The Hotel Had Not Verified My Age

The verification screen felt personal because it asked for personal evidence.

Its trigger was much less personal.

The site saw the hotel’s UK internet address and applied the rules associated with that region. The captive portal delayed the VPN connection, while the browser carried the hotel-created verification session forward after the route changed.

The useful sequence was simple: complete the hotel login, connect the VPN, open a clean browser session and use a route that survives the next Wi-Fi interruption.

My first provider changed the country but could not hold the session together. The smaller app removed the age-check trigger and kept the page moving when the hotel network weakened again.

The hotel had not decided I was underage. It had introduced me through a British address—and the problem ended when OnlydogVPN stopped the session from returning there.