<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title"></title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="122020" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="10/10/2021" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="824,190,972,592" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20211010T000000+5.30" edition.name="Main Edition" edition.area="MAI" position.section="DST10102102MAI-NEWS" position.sequence="2" ex-ref="DST10102102MAI-NEWS.indd" />
  </head>
  <body>
<body.head>
      <hedline>
    	
       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
			</media>
</block>

     <p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Bold">Afp, </lang>
<lang  class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book Italic">San Francisco
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">Facebook on Friday said users around the world again had problems accessing its services for hours due to a tweak of its system, just days after a massive outage caused in a similar fashion.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">“Sincere apologies to anyone who wasn’t able to access our products in the last couple of hours,” a Facebook spokesperson told AFP about 21:30 GMT.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">“We fixed the issue, and everything should be back to normal now.”
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">Website trouble tracker DownDetector showed spikes in reports of problems accessing or using Facebook and its photo-centric Instagram network as well as Messenger and WhatsApp starting about three hours earlier.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">Facebook attributed the trouble to a configuration change at its computing platform and said that it affected users of the social network and  Instagram, Messenger and Workplace globally.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">People flocked to Twitter to voice frustration.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">“What’s up with Instagram?” read a tweet that included a picture of cartoon character Bart Simpson sitting in a corner in apparent punishment.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">“It’s not even 4 days and it’s already down again.”
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">“Problems with Instagram, Facebook, Facebook Messenger and WhatsApp AGAIN!” read a lament in a DownDetector chat forum.
</lang>
</p>
<p style=".Bodylaser">
	<lang class="3" style=".Bodylaser" font="ITC Giovanni Std" fontStyle="Book">Hundreds of millions of people were unable to access Facebook, Instagram or WhatsApp for more than six hours on Monday, underscoring the world’s reliance on platforms owned by the Silicon Valley giant.
</lang>
</p>

    </body.content>
  </body>
</nitf>