<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WildFire Capacity Issues - Confirmed by Palo Alto SE in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10540#M7765</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another configuration option I would like to see is the ability to push the Wildfire updates to have any minute as the start time instead of forcing them on the exact quarter hour.&amp;nbsp; We use this scheduling offsets for the other updates to prevent conflicts.&amp;nbsp; I'm sure that everyone hitting at precisely the same time is at least part of the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 28 Jun 2014 00:02:48 GMT</pubDate>
    <dc:creator>pulukas</dc:creator>
    <dc:date>2014-06-28T00:02:48Z</dc:date>
    <item>
      <title>WildFire Capacity Issues - Confirmed by Palo Alto SE</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10537#M7762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apparently Palo Alto have confirmed that there are times when WildFire is simply too busy to serve all update requests (we've been seeing frequent failures).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone from Palo Alto comment on what the capacity situation is, what is being done to resolve it, and when the upgrades are expected to be in place by please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's a &lt;EM&gt;&lt;STRONG&gt;fantastic&lt;/STRONG&gt;&lt;/EM&gt; service but it's frustrating to keep getting emails from our PAN telling us that an update failed - we are paying for it at the end of the day :smileygrin:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 16:45:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10537#M7762</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-06-26T16:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: WildFire Capacity Issues - Confirmed by Palo Alto SE</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10538#M7763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Easy solution; lower the price for the WF-500 appliance from the idiotic high price it has to day, to a reasonable price. Then cutsomers will buy the appliance, wildfire cloud get less work - and everyone's happy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2014 06:58:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10538#M7763</guid>
      <dc:creator>pivvre</dc:creator>
      <dc:date>2014-06-27T06:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: WildFire Capacity Issues - Confirmed by Palo Alto SE</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10539#M7764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Honestly, I can live with capacity issue if it's communicated properly and a fix is in site.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's pretty much unacceptable is a week of back and forth with support with seemingly random suggestions with me repeatedly asking for it to be escalated to Palo Alto only to be told after a week "Oh they've said it's capacity issues" - which was the first thing I asked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2014 07:03:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10539#M7764</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-06-27T07:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: WildFire Capacity Issues - Confirmed by Palo Alto SE</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10540#M7765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another configuration option I would like to see is the ability to push the Wildfire updates to have any minute as the start time instead of forcing them on the exact quarter hour.&amp;nbsp; We use this scheduling offsets for the other updates to prevent conflicts.&amp;nbsp; I'm sure that everyone hitting at precisely the same time is at least part of the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Jun 2014 00:02:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wildfire-capacity-issues-confirmed-by-palo-alto-se/m-p/10540#M7765</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-06-28T00:02:48Z</dc:date>
    </item>
  </channel>
</rss>

