Information
Name: PITCHBLACK
Author: aismallard
Rating: 322/376
Created at: Tue Jan 21 2020
Special Containment Procedures

Service availability during SCP-5900.
RAISA's Surveillance Division is determining the cause of SCP-5900 (ticket #E4K07U2) and creating technical countermeasures to reduce the severity of a similar event in the future (ticket #30VNI4F). The SCP-5900 Containment Director is assigning technicians to replace all damaged components and investigate suspect auxiliaries.
The Department of Internal Security has opened an investigation. [DATA REDACTED 5/INTSEC]
Description
SCP-5900 was an outage of PANOPTICON, lasting for five days from 2022/05/19 12:15 to 2022/05/24 21:20 UTC. During this time, surveillance satellites, Site-07 communications, intelligence processing, and IntSCPFN file sync were inoperable. The full extent and nature of the anomaly are presently unknown.
Addendum 5900.1
PANOPTICON PROJECT BRIEF
Project #
RAISA-31409
Authorized By

Relay installed at the base of a streetlamp

Protected Site-07
Overseer Council
PANOPTICON refers to a number of interconnected technological and paratechnological constructs, which collectively enable global oversight.
The Atreus Satellite Array is a Foundation-launched fleet of modular satellites, with orbits configured to ensure full coverage of the Earth at all times. Each satellite has a surveillance installation (see 4/PANOPTICON/HDW04 for schematics), including X-ray antennas and Kant receivers. They also have several hardpoints for weapons and reality anchor attachments, set at the direction of the Department of Applied Force.
Additionally, the Department of Applied Influence's Field Monitoring Division is responsible for the installation and maintenance of over ██ million input devices, including SEP-shielded cameras, microphones, links into existing civilian and government surveillance systems, thaumaturgic particle detectors, and Kant counters.
All gathered surveillance information is processed at Site-07, located in the Norton Bay off the coast of Alaska. Due to its secure location and increasing role in Foundation archival operations, it was established as the headquarters of RAISA in 1970. Fifteen years later, the DEEPWELL backup system entered service there as well.
Records are loaded into an anomalous RDBMS (relational database management system) and indexed accordingly. SKYEYE.aic continuously queries this database to look for correlations or abnormalities which may indicate potential extranormal events, objects, or activity by groups of interest.
On 19██/12/12 a thaumaturgic ritual was performed at the direction of the Overseer Council, resulting in metaphysical anchoring constructs being embedded within areas of the infosphere associated with the Foundation, normalcy, and knowledge.
As information is duplicated throughout all PANOPTICON nodes with at least three parallel processing sites each, an extended outage is extremely improbable. Combined with the anchoring constructs, the calculated probability of an outage is less than 1 in 1024.
All components of the metaphysical anchoring system were found to be active during SCP-5900.
Addendum 5900.2
SERVICE LOGS
The following is a selection of log events submitted to the Site-07 governance mainframe at the incidence of SCP-5900.
Addendum 5900.3
INTERNAL COMMUNICATIONS
The following are selections from engineering ROMP1 channels at Site-07 during SCP-5900.
Excerpt: Day 1, 4:17 AM (local time)
morning graveyard shift people hey terry hey, what's up got a bit of a headache, you? rhill uploaded file: 1560131817.jpg ⬇
pffft made me almost spurt coffee out of my nose lol mission accomplished :D .rebuild supply-service Starting build #839057 for supply-service lgonzales: you adjusted the config already, right? yeah i did sweet Monitor: webcrawler-service is DOWN Monitor: intscpfn-server is DOWN Monitor: intscpfn-node is DOWN Monitor: communications is DOWN Monitor: slot-service is DOWN Monitor: bridge-aic is DEGRADED Monitor: relay-service is DOWN Monitor: backup-service is DEGRADED Monitor: poi-service is DOWN what the fuck Monitor: message-service is DEGRADED Monitor: intel-storage-service is DOWN Monitor: skyeye-aic is DEGRADED can someone stop it from spamming Monitor: linguist-aic is DOWN jtaylor kicked raisa-bot.
I'll look and see what's wrong with the bot uh why is the site locking down? is there a drill? wtf the python webcrawlers are actually broken no way Lost external network access. Switching ROMP to site-only.
yeah I can't connect to the panopticon spy nodes. something's up raisa-bot has joined.
COMMAND.aic broadcast: Extensive outage in effect. RAISA command has been notified. fuck.
Excerpt: Day 1, 6:41 AM
all right, so here's how management has decided to set this up team A will look through the broken services team B goes through all our deploys team C looks at the metabed anchor system classifications are still in force, so please report any unintentional contact with level-4/5 intel sounds good, I'll take filesync jtaylor: isn't there a provisional scp for this incident? uh yes, there should be. I don't see it though the local database was in the middle of a sync and got corrupted command.aic wasn't able to save the provisional skip anywhere can we just roll it back? yeah, give me a moment jjohnson uploaded file: scp-report-1560142360.ftml ⬇
wow, why was it given "scp-5900"? i guess we've never had a slot-assign outage before lol okay, so we can see all the satellites above us, but just can't connect for some reason we can connect directly, right? yes. big pain in the arse though actually jim has a script to help with that. lemme see the technicians just finished inspecting the shortwave radio antennas. doesn't look like there's any damage that's good at least so we're pretty sure it's a software or configuration problem hey all, I was able to connect to satellite atreus-48. status normal, no connections to other sites no extraterrestrial abnormalities upload the report here? sure, give me a sec rhill uploaded file: atreus-48-events.log ⬇
rhill uploaded file: atreus-48-space.ftml ⬇
the ground data is loading really slow, but nothing weird so far why do we care about surface readings? don't we just want connection logs? we don't know if this is a k-class oh
Excerpt: Day 2, 4:38 PM
man this thaumaturgy link code is really hard to understand I know it's old, but it's not that bad, is it? oh it's fine, I just forgot how hard it is to wrap your head around this stuff lol you went to ICSUT, right? did you take that paratemporal networking class? jjohnson indeed. consuming packets before you've sent them was the hardest part for me how are the satellite systems looking? the links have been operable for hours but the system still can't do the handshake I'm really not sure. I've been running local experiments and they work fine, but once we plug into the real system it fails maybe something wrong with our thaumic keys? hmm. will be hard to make new ones though, given the lack of communications here this is interesting so metabed has several conceptual hooks for protecting our systems, right all of them are "latched on" so to speak, but a few aren't "transferring"? the model is weird, if you know about alpha-lambda loops you know what I'm talking about what how? there aren't many declassified docs but that is only possible if the originator decides to decouple iirc which I highly doubt the O5s would do I know, it's bizarre maybe a third party tried to take it from us? nah, it would require way too much energy though I think looking at swapping out conceptual targets is a possibility. jtaylor can you get me access to the 5/metabed ritual info? I'll see what I can do
Excerpt: Day 5, 1:08 PM
The administrative liaison is saying you can formulate a new thaumic unit, but it can't be overlapping with the originals wtf? my plan doesn't, it attaches to uniq-418ef and uniq-0a341 tell them to just give me the full fucking plans and they can amnesticize me after I've already told you that isn't going to happen this is such bullshit fundamental rituals are always safeguarded the most jjohnson I didn't ask you sorry, that was uncalled for I think we can at least restore the satellite connections with conceptual positioning those plans would be helpful there at least to be honest, I don't even believe the documentation. it claims they attach to "the concept of knowledge" but I doubt it. that's too fundamental, they probably just got some "sending data" side-stream. way easier to do and it would explain why it being interrupted fucked all our comms is it interrupted? what else could it be? it's not broken or the system would've repaired and it's not detached since I just checked lgonzales: some good news. maria jones is stepping in and giving us access to the ritual plans don't burn me here, we better get something substantial from this oh thank god jtaylor uploaded file: [DATA REDACTED 5/PANOPTICON] ⬇
holy shit, look at that god damn they weren't lying we can fix this now. rhill you have that great ritual autoexecutor tool, right? it's standard now, renamed to "thaumexec" excellent so let's reconfigure on the main anchor points, with the proposed backups just started it uh guys, the monitor is saying the network has abnormally high input? Monitor: communications is UP wait the system is working again? Monitor: bridge-aic is UP Monitor: linguist-aic is RECOVERING Monitor: intscpfn-server is UP Monitor: intscpfn-node is UP holy shit it worked! Monitor: slot-service is UP Monitor: relay-service is UP :D Monitor: webcrawler-service is UP Monitor: backup-service is UP we're getting atreus update events. looks like things are starting to flow again good work everybody
Addendum 5900.4
RECOVERY UPDATE
Critical services began recovering at 2022/05/24 21:09 UTC, after which the PANOPTICON metaphysical anchoring system automatically recalibrated itself. An inspection discovered an unusual HTML payload in one of the anchor's logs. A screenshot has been attached below:
The origin and meaning of this notice is unclear. Investigation is ongoing.
PREVIOUS
« SCP-6781: HERITAGE »
aismallard's Works
SCP-8998 •
SCP-8178 •
SCP-9201 •
SCP-6115 •
SCP-5510 •
SCP-4339 •
SCP-4781 •
SCP-4838 •
SCP-9306 •
SCP-5134 •
SCP-4322 •
SCP-4853 •
SCP-5446 •