The time when the BGP update was generated, as set by the BGP monitor or route collector service.
If present, redirects to a corresponding Hijack entry.
Blue "eye" if the detector has seen the BGP update and the update is already handled, grey if examination is pending. *Note that since ARTEMIS is a real-time system, if the detector is not active when the monitor captures and incoming BGP update, the update will never be handled in the future. If you need it handled you need to replay it from historical logs, "live" (with the detector active).
Additional information under "More" tab:
Format [ASN:comm_id, ...]. BGP communities related to the BGP update.
The original path of the BGP update. This is different from the reported AS Path only in the case where the BGP update is an announcement of a path containing AS-SETs of SEQUENCES, and the monitor microservice decomposes the update into multiple updates (with simple paths per update) for ease of interpretation and handling.
Unique identifier/key of hijack event.
The longest prefix that matched a rule in the configuration file. Note that this might differ from the actually hijacked prefix contained in the BGP update in the case of a sub-prefix hijack event.
Same as the "Hijack" field in the main table.
Same as the "Status" field in the main table.