A notification service can recover for one device or channel while another still lags. State the event that should trigger a notification, the event time, expected channel, actual arrival time, and whether the underlying event itself completed. Use a harmless test where possible.
Check notification permissions and quiet-hour settings, but do not assume they explain a sudden widespread delay. Keep private message content, device tokens, and account details out of a public report. Compare app, email, and web notifications separately if the service supports them. Check official incident updates, and report the channels that remain delayed rather than saying only “fixed for me.”