Habr•October 8, 2026•🇷🇺Translated from Russian

macOS User Investigates Claude Regional Block via Logs and Restores Work Site Access with Targeted WireGuard Routes

A macOS user conducted an in-depth analysis of Claude application logs following repeated regional availability errors after enabling WireGuard VPN. The review began in the ~/Library/Logs/Claude/ directory, where repeated markers such as app-unavailable-in-region, region_unavailable, and “Claude isn’t available in your region” appeared across web log files.

Using rg searches, the user identified 1,264 lines in the primary log plus 2,891 lines across rotations. Nine specific dates were examined in detail, revealing some errors occurred immediately after Mac wake-ups and others near WireGuard activity. The most notable cluster appeared on September 29, two days before the account restriction.

Despite the timeline correlation, no conclusive proof connected the VPN tunnel to the block. WireGuard’s tunnel-log.bin contained only 2,048 ring-buffer entries, all overwritten by October 3, erasing September data. macOS system containers frequently returned “Operation not permitted” when accessed. The (direct) marker in Claude logs referred solely to internal HTTP proxy selection and did not indicate whether traffic traversed the system VPN.

While troubleshooting Claude, a second problem emerged: several work services became unreachable over WireGuard. amoCRM, TGBooster (including its CDN), and Geekjob all timed out. Comparative curl tests using the physical en0 interface versus the VPN route confirmed that the same destinations returned HTTP 200 when bypassing the tunnel.

Initial attempts to route only Claude domains through the VPN failed because downloads.claude.ai resolved to addresses absent from published network lists. The approach was reversed: WireGuard remained the default route while explicit host routes directed verified work IPs through the local gateway at 192.168.100.1. Ten such routes were added for amoCRM, TGBooster, and Geekjob after verifying each with route get commands.

A temporary PF kill-switch policy was implemented to block direct egress if the tunnel dropped. The ruleset was managed by a launchd service that monitored the WireGuard interface and restored routes. Although initial manual tests succeeded, the service entered a loop on October 5, repeatedly detecting “Own anchor/table changed” and “Own PF hook/order missing,” ultimately severing all connectivity. The service was disabled, original /etc/pf.conf restored, and custom routes reapplied via a separate script.

By October 8, verified work-site addresses remained reachable under active WireGuard while selected Claude endpoints continued through the tunnel. No persistent kill-switch solution survived sleep/wake cycles or network changes, leaving that requirement open.

Related articles

AntiMalware•Other

Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour

A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.

AntiMalware•Other

Yandex Tests Compass Device for Taxi Navigation During GPS Outages

Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.

Habr•Other

Apple Attributes Widespread Service Outage to Faulty Internal IT Update

Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.

Habr•Other

Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay

On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.