Sanitize external calendar feeds before they reach your corporate Exchange/M365 environment. Zero-persistence proxy.
Paste the URL of your broken calendar feed
Detect 36+ RFC 5545 violations including missing VTIMEZONEs, broken RRULEs, and invalid UIDs. Get detailed error report.
Our repair engine automatically detects and remediates these common failures found in Enterprise calendar feeds at the network edge.
Calendar feed lacks VTIMEZONE definition for non-UTC times
Impact
Events appear at wrong time on iOS/Android (typically 4-8 hours off)
How Lokr Fixes It
We inject RFC 5545-compliant VTIMEZONE blocks automatically
RFC 5545 §3.6.5 requires VTIMEZONE components for all non-UTC DATETIME values
Events lack unique identifier property
Impact
Calendar clients reject events or create duplicates on every sync
How Lokr Fixes It
We generate RFC 4122-compliant UUIDs for all events
RFC 5545 §3.8.4.7 mandates UID property for all VEVENT components
Multiple events share the same UID causing sync conflicts
Impact
Calendar clients show only one event, others disappear or flicker
How Lokr Fixes It
We deduplicate UIDs and append unique suffixes where needed
RFC 5545 §3.8.4.7 requires UID to be globally unique
Events lack start time property
Impact
Calendar clients reject event or default to epoch time (Jan 1, 1970)
How Lokr Fixes It
We inject DTSTART using DTSTAMP or current time as fallback
RFC 5545 §3.6.1 requires DTSTART for all VEVENT components
UNTIL date type doesn't match DTSTART type (DATE vs DATETIME)
Impact
Recurring events end prematurely or extend indefinitely
How Lokr Fixes It
We normalize UNTIL to match DTSTART type and timezone
RFC 5545 §3.3.10 requires UNTIL to match DTSTART value type
DTSTART is DATE but DTEND is DATETIME (or vice versa)
Impact
Events show incorrect duration or fail to render
How Lokr Fixes It
We normalize both to same type, preferring DTSTART type
RFC 5545 §3.6.1 requires DTSTART and DTEND to have same value type
Need a deep dive into all 36+ RFC violations we support?
Legacy formats and device fragmentation break your infrastructure. Standardize your delivery layer today.
Teams across APAC, EMEA, and AMER struggle with training times appearing incorrectly on local devices.
Enterprise data privacy requires strict controls. General ICS feeds expose too much metadata.
IT teams are overwhelmed with 'why isn't this training on my calendar?' tickets.
Specialized infrastructure to remediate vertical-specific edge cases.
We rewrite VTIMEZONE definitions on the fly, ensuring a 9am meeting in London shows up as 9am in London, regardless of where the device is.
Strip sensitive PII and internal descriptions from external calendar subscriptions automatically.
Connect Workday, SAP, Oracle, and Google Workspace seamlessly.
We don't sell to end-users. We build for the engineers and admins who have to keep the systems running.
"Syncing our Exchange on-prem environment with our new Google Workspace acquisition was a nightmare. Lokr normalized the feeds instantly."
David K.
Global IT Manager, Financial Services
"We needed to expose Workday time-off calendars to managers' Outlook without complex integrations. Lokr handled the ICS translation perfectly."
Sarah M.
HRIS Architect, Global Manufacturing
"SAML-protected calendars were breaking our digital signage. Lokr provided a secure, tokenized proxy that played nice with our display hardware."
Priya P.
Workplace Tech Lead, Enterprise Software
Diagnose errors and test the fix instantly.
Fix one critical feed.
Department-wide infrastructure.
Organization-wide infrastructure.
Most large organizations choose Enterprise for custom security SLAs and BAA execution.
Ready to secure your global calendar infrastructure?
Contact Sales, we’ll set up your perfect feed today.
Launch a production-grade proxy with Zero-Persistence security.
Review technical standards across Higher Ed, Logistics, and Enterprise IT.
Step-by-step remediation for Canvas, Greenhouse, Ellucian, and PeopleSoft.