 Item number SCP-579 Object Class Keter Special Containment Procedures SCP-579 is currently in Site 62C, a compound located approximately 80 kilometers from Site 1, the main site. Knowledge of the existence of this site has been deemed unnecessary for all non-essential personnel who are not involved in SCP-579's containment. Site consists of building, housing SCP-579, and living quarters for containment staff. SCP-579 is encased in a 30 meter by 30 meter by 30 meter unit, made of data expunged, in which SCP-579 is kept in permanent suspension through use of electromagnets. Is equipped with hard line to high command, through which all reports and notifications are to be made. Staff consists of two teams, each composed of 17 level 1 personnel, 3 level 2 personnel, and 1 level 4 personnel, which are rotated bi-weekly. All instruments are to be checked each half hour to ensure their continued function. Routines and any measured attribute are to be immediately reported to high command. Any instrument or electronic device registering more than 0.2 percent from its median range of function, or displaying any errors or lapses in functioning, will result in automatic execution of Action 326 Israfil. Routine reports to high command are to be made hourly. If a report is not received within 7 minutes of its scheduled time, Action 10 Israfil A is to be executed. Absolutely no action regarding SCP-579, other than those strictly outlined above, is to be taken. Description. Data Expunged. Addendum 579001. Action 10 Israfil A. Doors, windows, and other possible exits from site are to be sealed, granting the transfer of personnel into or out of the site. Teams and resources required for Action 10 Israfil B are to be readied and moved into position. If reports are received by high command at the correct time, or if instruments or electronic devices return to their normal state, high command will issue an all clear statement. If such a statement is not received within 7 minutes of the commencement of Action 10 Israfil A, execute Action 10 Israfil B. If, at any time, any instruments or electronic devices near SCP-579 begin to display significant errors or deviations from normal functioning, Action 10 Israfil B must be executed immediately. If an all clear statement is issued, at least 72 hours without further anomalies must pass before site can be unsealed and Action 10 Israfil B teams may stand down. Action 10 Israfil B. Gateway of Site 62, SCP-004, is to be destroyed. This must be done regardless of personnel or facilities remaining within the site. Remnants of the gateway, or the gateway itself, if destruction proves impossible, are to be contained in the same manner as SCP-579. High command will then issue further instruction. Addendum 579002. In the event of a successful Action 10 Israfil B, all sealed documents regarding SCP-579 are to be released to all personnel involved with the action. Procedures as outlined within the documents are to be followed, along with contingency plans if necessary. Be aware that even with the successful execution of Action 10 Israfil B, estimates place the occurrence of data expunged at one year or less. If SCP-579 is mentioned in any capacity by SCP-004, any anti-foundation or public groups or data expunged, it is recommended that Action 10 Israfil A be executed as planned immediately. In the event of an unsuccessful Action 10 Israfil B, no further action will be necessary. Data Expunged. Addendum 579 Timeline. Event 0. SCP-579 is discovered. Point of origin is data expunged. Event 1. Initial assessment of SCP-579 is undertaken. Event 2. SCP-579 is inadvertently removed from its point of origin. Events 3 through 7. Data Expunged. Event 8. SCP-579 is successfully contained. Event 9. SCP-579 is moved to Site 4. Event 10. Containment failed. Loss of Site 4. Event 11. SCP-579 is successfully contained. Event 12. SCP-579 is moved to Site 31. Event 13. Containment failed. Loss of Site 31. Event 14. SCP-579 is successfully contained. Event 15. SCP-579 is moved to Site 26. Event 16. Containment failed. Loss of Site 26. Event 17. SCP-579 is successfully contained. Event 18. Attempt is made to destroy SCP-579. Attempt failed. Event 19. Attempt is made to destroy SCP-579. Attempt failed. Event 20. Attempt is made to destroy SCP-579. Attempt failed. Event 21. Attempt is made to destroy SCP-579. Attempt failed. Event 22. Containment failed. Events 23 and 24. Data expunged. Event 25. SCP-579 is successfully contained. Event 26. SCP-579 is transported to vicinity of Point of Origin. Event 27. Attempted to return SCP-579 to Point of Origin. Attempt failed. Event 28. Attempted to return SCP-579 to Point of Origin. Attempt failed. Event 29. Attempted to return SCP-579 to Point of Origin. Attempt failed. Event 30. Attempted to return SCP-579 to Point of Origin. Attempt failed, resulting in the loss of Point of Origin. Event 31, containment failed. Events 32 through 35, data expunged. Event 36, SCP-579 is successfully contained. Event 37, SCP-579 is moved to Site- Event 38, SCP-579 undergoes previously unobserved changes, believed to involve data expunged. Containment holds, though this is determined not to be attributable to containment procedure. Event 39, High Command issues lockdown on Site- Event 40, Agent M formulates current containment plan. Event 41, Site-62-C is constructed. Event 42, SCP-579 is moved to Site- Event 43, High Command seals all data not needed for containment of SCP-579. Termination of agents to prevent data leakage regarding SCP-579 is deemed unnecessary, as only seven such agents remain. Said agents are retained as advisors, should future events concerning SCP-579 occur. Lesson complete. If you missed the previous orientation, go watch SCP-578, Blood Opals, right now. Or for the complete course, watch this playlist.