Root URL returns HTTP 418 to Meta crawler

We are hosting a static site via Netlify Drop.

The site loads normally for many users, but some users and Instagram cannot access it reliably.

Meta Sharing Debugger returns HTTP 418 for:

https://migaway.com

but returns 206 for:

https://migaway.com/index.html

and:

https://migaway.com/?v=2

DNS, SSL, firewall, WAF, and domain propagation are all confirmed healthy.

Please investigate edge caching or root-route behavior for the custom domain

Subject: Root URL returns HTTP 418 to Meta crawler

Hello,

I am hosting a static website on Netlify:

https://migaway.com

The site loads normally for many users, but some users and Instagram cannot access it reliably.

We investigated extensively and found:

- DNS configuration is correct.

- SSL certificate is valid.

- Domain propagation is complete.

- WAF is disabled.

- Firewall rules are disabled.

- Site is deployed using Netlify Drop.

Meta Sharing Debugger reports:

Response code: 418

However:

https://migaway.com/index.html

Response code: 206

and

Response code: 206

Meta can successfully scrape the page title and metadata, but the root URL continues returning HTTP 418.

This appears to affect Instagram link accessibility as well as some users on specific networks/devices.

Could you please investigate any edge caching, routing, or root URL behavior associated with this site?

Site:

Netlify site:

chipper-pavlova-629da6

Thank you.

Meta Sharing Debugger intermittently receives HTTP 418

for https://migaway.com

while the exact same deployed content receives 206

for MIGA — Lisbon Girls Trip Concierge

and MIGA — Lisbon Girls Trip Concierge