Review this week
Registration source updated
Review registration-sensitive wording against current application, renewal, or operating assumptions.
Open registration updatePortland monthly recap
What changed in Portland STR rules in March 2026.
March was a strong Portland proof month because it showed two things at once: permit-sensitive sources moved, and fallback documents mattered because several primary official pages were blocked. This recap turns that month into one readable summary before you decide whether Portland deserves ongoing monitoring.
March 2026
The Portland changes worth reviewing first
Review this week
Permit fallback source updated
Use the fallback-backed permit update when blocked primary pages would otherwise delay review work.
Open permit updateContext
Primary pages stayed degraded
Fallback activity mattered more this month because several primary official Portland pages remained blocked in monitoring.
See coverage statusWho was likely affected
This month mattered most to hosts and operators working from permit assumptions
Permit applicants
Anyone with active or pending Portland permit work had reason to compare the latest wording against current assumptions.
Renewal-sensitive operators
Operators already in market had the most reason to review whether updated guidance changed how they interpret current status or timing.
Teams relying on primary pages
Portland mattered most when your workflow depended on not missing blocked-primary-page changes during the same week.
Validate it yourself
Use the official-source path before you treat Portland as urgent
1
Open the city preview
See the current monitored-source roster, fallback health, and which Portland item sits highest in the queue.
2
Open the update page
Use the update page to see why the change matters and who is likely affected first.
3
Click the official fallback source
Compare the monitored fallback document to the summary before treating the change as operationally important.