<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/ab62ad5ede554993b398691971aac266&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ab62ad5ede554993b398691971aac266-1627288277498.gif</thumbnail_url><duration>130</duration><title>Zipy - OnlineOffline/NetworkReqResHeaders</title><description>With this you can now see how some of the issues your users face is not because of you but because they had network issues. Zipy lets you identify your API errors from Network issues using Offline/Online feature. We also have more details in the Request/Response headers - try our Dev Tools Network Tab.</description></oembed>