Social Media Remote Team Uptime

This dataset provides a detailed log of API uptime and operational incidents for distributed social media teams managing platform integrations. It enables technical leads and SMB operators to monitor service reliability, coordinate incident response, and benchmark platform stability across remote teams and social media channels.

  • last updated 8 Jan 2026
  • by GoMask
The brief that made it

Monitor and benchmark API uptime and platform stability across remote teams

Sample rows

preview · 8 of 60 rows · all 18 columns
incident_idstringseveritystringaffected_users_countintegeris_benchmark_eventbooleanreported_bystringteam_idstringteam_namestringplatform_namestringintegration_namestringincident_typestringstatusstringstart_timedatetimeend_timedatetimeduration_minutesfloatroot_causestringresolution_stepsstringnotified_atdatetimedescriptionstring
INC1001info0truejames.leeTEAM-A1Global IntegratorsFacebookPost Scheduleruptimemonitoring2024-06-01T09:00:00Z2024-06-01T17:00:00Z480blankRoutine system health checks performed.2024-06-01T08:30:00ZScheduled maintenance window, no service interruption.
INC1002major900falsemaria.santosTEAM-B2Pacific OpsInstagramAnalytics Fetcherdowntimeopen2024-06-02T14:15:00ZblankblankUpstream service outage.blank2024-06-02T14:20:00ZAPI unresponsive due to upstream timeout.
INC1003minor120falsesophie.dupontTEAM-C3EMEA ConnectorsLinkedInComment Moderationdegradationresolved2024-06-03T11:00:00Z2024-06-03T12:30:00Z90High traffic volume.Scaled up worker processes.2024-06-03T11:05:00ZDelayed moderation queue processing.
INC1004critical1500falselucas.martinezTEAM-D4Americas ResponseTikTokAd Campaign Syncdowntimeresolved2024-06-04T21:45:00Z2024-06-04T23:15:00Z90Expired SSL certificate.Renewed certificate and restarted services.2024-06-04T21:50:00ZDatabase connection failure affecting ad sync.
INC1005info0trueananya.guptaTEAM-E5Asia Pacific TeamTwitterDirect Message Relayuptimemonitoring2024-06-05T03:00:00Z2024-06-05T09:00:00Z360blankRoutine monitoring performed.2024-06-05T02:55:00ZNormal operational hours, no incidents reported.
INC1006major340falseoliver.larssonTEAM-F6Nordic SystemsYouTubeVideo Uploaderdegradationacknowledged2024-06-06T16:45:00Z2024-06-06T18:00:00Z75Bandwidth throttling detected.Contacted ISP for resolution.2024-06-06T16:50:00ZUpload speed significantly reduced.
INC1007info0truemaria.santosTEAM-B2Pacific OpsFacebookPost Scheduleruptimemonitoring2024-06-07T09:00:00Z2024-06-07T17:00:00Z480blankAutomated health checks passed.2024-06-07T08:55:00ZAll services operational.
INC1008critical1100falsesophie.dupontTEAM-C3EMEA ConnectorsInstagramAnalytics Fetcherdowntimeopen2024-06-08T13:20:00ZblankblankInvalid API token.blank2024-06-08T13:25:00ZService unavailable due to authentication error.

What the 60 rows show

from the 60-row sample

Critical severity stands out: mean affected_users_count is 974.0, against 146.2 for the rest.

  • 37%is_benchmark_event = true
  • 92.5median affected_users_count
  • 3incident types
  • 4statuses
  • 7platform names
  • 13integration names
Mean affected_users_count by severity60 rows
05001,000974.0critical10 rows392.2major16 rows79.6minor13 rows0.0info21 rows
affected_users_count60 rows, in bands of 200
0204038633611208001,600affected_users_count →

Median 92.5, from 0 to 1,500.

reported_by60 rows · top 10 of 16 values
  1. james.lee5
  2. maria.santos5
  3. sophie.dupont5
  4. lucas.martinez5
  5. ananya.gupta5
  6. oliver.larsson5
  7. [email protected]4
  8. [email protected]4
  9. [email protected]4
  10. [email protected]3
18 columns by typefrom the column list below
  • string 12
  • integer 1
  • float 1
  • datetime 3
  • boolean 1

Columns

18 columns in four groups
blueprint · 18 columns
columntypedescriptionexample
Text 12 columns
incident_idstringUnique identifier for each operational incident or uptime event.uniqueINC1001
team_idstringUnique identifier for the remote team responsible for the integration.TEAM-A1
team_namestringName of the remote team managing the platform integration.Global Integrators
platform_namestringName of the social media platform being integrated (e.g., Facebook, Twitter, LinkedIn).7 valuesFacebook
integration_namestringName of the specific API integration or service (e.g., Post Scheduler, Analytics Fetcher).Post Scheduler
incident_typestringType of event: 'uptime', 'downtime', or 'degradation'.uptime · downtime · degradationuptime
statusstringCurrent status of the incident (e.g., open, resolved, monitoring).open · resolved · monitoring · acknowledgedmonitoring
severitystringSeverity level of the incident (e.g., critical, major, minor, info).critical · major · minor · info · optionalinfo
descriptionstringDetailed description of the incident, impact, and context.optionalScheduled maintenance win…
root_causestringIdentified root cause of the incident (if known).optionalUpstream service outage.
resolution_stepsstringSummary of steps taken to resolve the incident.optionalVerified sync logs.
reported_bystringName or identifier of the person who reported the incident.optionaljames.lee
Numbers 2 columns
duration_minutesfloatDuration of the incident or uptime period in minutes.0 or more · optional480
affected_users_countintegerNumber of end-users affected by the incident.0 or more · optional0
Dates and times 3 columns
start_timedatetimeTimestamp when the incident or uptime period started.2024-06-01T09:00:00Z
end_timedatetimeTimestamp when the incident or uptime period ended (null if ongoing).optional2024-06-01T17:00:00Z
notified_atdatetimeTimestamp when the incident was communicated to stakeholders.optional2024-06-01T08:30:00Z
True or false 1 column
is_benchmark_eventbooleanIndicates if this incident/event is used for benchmarking platform stability.optionaltrue

Use it for

  • is benchmark e…37%22 of 60 rowsmean affected users c…974.0crit…392.2major79.6minor0.0info

    A technology dashboard

    The is_benchmark_event rate, affected_users_count by severity and a breakdown of reported_by. Excel, Power BI or Tableau.

  • Why do the 10 critical rows have a mean affected_users_count of 974.0?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable incidents with team_id, team_name and platform_name to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset60 rows18 columns
Yours1,000 rows18 columns

blueprint · social-media-remote-team-uptime

Behind this dataset

Same schema. As many rows as you need.

These 60 rows came out of a blueprint — 18 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row represents a 24-hour period per team.
  • Log uptime percentage, incidents, and resolution time.
  • Include API endpoint, timezone, and incident severity.
  • Capture remote team lead and number of affected users.
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
social-media-remote-team-uptime

More in Technology

Browse all
Also in TechnologyRemote Team Cybersecurity Incident LogsConsumer Mobile App Usage StatsCustomer Support Ticket ResolutionAll 1,967 datasets

What should your data show?

Preview 20 rows free
No signup. No card.