Status updates | WeInvoice Incidents and maintenance reported on status page for WeInvoice https://status.weinvoice.fr/ https://d1lppblt9t2x15.cloudfront.net/logos/8a29d84c84845261aed39078a6d241b0.png Status updates | WeInvoice https://status.weinvoice.fr/ en More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1044756 Tue, 01 Sep 2026 11:31:26 -0000 https://status.weinvoice.fr/incident/1044756#1de1679d2e6d20bccdc2953ce5db0efcf2129fadbf76f6c5514a24c3890bd381 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1044756 Tue, 01 Sep 2026 09:51:27 -0000 https://status.weinvoice.fr/incident/1044756#9ab1de36537066e1801690deb5bad7dd63d1f5ae5e0476a264b6d9c7f4430b97 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — r https://status.weinvoice.fr/incident/1044543 Tue, 01 Sep 2026 07:34:28 -0000 https://status.weinvoice.fr/incident/1044543#0b5a9234ba47c1d7c375d37f152e959e11e6e31872f2891b9e2c67111dc48adb Incident More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — result="failure" excludes our own pacer refusals (throttled_self), so this is what the PROVIDER (or the network to it) did. Feeds the «Annuaire PISTE» component of status.weinvoice.fr via the statuspage label; resolves itself once live traffic succeeds again. More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — r https://status.weinvoice.fr/incident/1044543 Tue, 01 Sep 2026 07:29:28 -0000 https://status.weinvoice.fr/incident/1044543#028736769bef4968e20104d13452af8a04dfaf73de739ac5e0797c46b20eff50 Incident More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — result="failure" excludes our own pacer refusals (throttled_self), so this is what the PROVIDER (or the network to it) did. Feeds the «Annuaire PISTE» component of status.weinvoice.fr via the statuspage label; resolves itself once live traffic succeeds again. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1043374 Mon, 31 Aug 2026 17:16:26 -0000 https://status.weinvoice.fr/incident/1043374#bbad6a28868433212e614fb8982077d5e13be55ee72a0a64df4461da09b87a41 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1043374 Mon, 31 Aug 2026 17:06:26 -0000 https://status.weinvoice.fr/incident/1043374#9f9d612b69719606ba889653192f61541977467280faddb293e81e958c7584ba Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1043108 Mon, 31 Aug 2026 14:01:27 -0000 https://status.weinvoice.fr/incident/1043108#7edde54699b4c0bdda03c4fd194751878c2b29edfa3b86bd13d42bf0bb6e3bf5 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT rece https://status.weinvoice.fr/incident/1043108 Mon, 31 Aug 2026 13:51:26 -0000 https://status.weinvoice.fr/incident/1043108#9258575443480e2bd3cf5f24640bd2d21b7ec3fbded2aa149a965605ed123e91 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends) AND at least TWO DISTINCT receivers were affected. Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). The distinct-receiver gate comes from Loki (`pdp_peppol_ap_network_failure receiver=…`, emitted by PeppolApClientService on every network-path failure): the counter carries no receiver label — per-SIREN cardinality — so without it ONE counterpart whose SMP hiccups on a quiet window reads as a network outage and opens a PUBLIC incident (production 2026-08-28: 2 sends, 1 receiver, that SMP answered HTTP 200 minutes later). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1037547 Fri, 28 Aug 2026 13:01:26 -0000 https://status.weinvoice.fr/incident/1037547#22c4b548cc6889b47f207997b00dcc304a9b0927992bc429d18e223ab191ec67 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1037547 Fri, 28 Aug 2026 12:21:26 -0000 https://status.weinvoice.fr/incident/1037547#49502a0e9c376756c22d4904ff91658fb74fae842f5246f910dc48f6f4ea70a0 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1037290 Fri, 28 Aug 2026 08:46:26 -0000 https://status.weinvoice.fr/incident/1037290#c41f579830e50b6b66c853ed7af78e626856638577a5cb898160aa53e95c1f98 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1037290 Fri, 28 Aug 2026 08:36:26 -0000 https://status.weinvoice.fr/incident/1037290#cd256dca4ece780bc269f2c448e282f1c29d1c7003c0a1f3bf307b4d8fae507e Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1036634 Thu, 27 Aug 2026 22:16:26 -0000 https://status.weinvoice.fr/incident/1036634#7384b30628404bc66871e6421bb88f8c1dea914932015df5afecb7ad02935593 Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_ https://status.weinvoice.fr/incident/1036634 Thu, 27 Aug 2026 21:51:26 -0000 https://status.weinvoice.fr/incident/1036634#681fbd157d526a46c669b1b2acba13a1ec68322366485d89387047cb58b9448f Incident More than half of the outbound Peppol AP send attempts of the last 30 min ended on a NETWORK failure path (min 2 sends). Read from pdp_peppol_ap_send_total — numerator and denominator both EXCLUDE `unconfigured`, `loopback_refused` AND `input_mismatch` (none of those reached the network; an input_mismatch spike is OUR converter regression and must never open a public «Réseau Peppol» incident). Complements the two Loki-backed peppol-reporting rules (which watch the monthly OpenPeppol reporting job, a different leg). Feeds the «Réseau Peppol» status-page component. More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — r https://status.weinvoice.fr/incident/1032452 Tue, 25 Aug 2026 12:06:30 -0000 https://status.weinvoice.fr/incident/1032452#8cfc4a52024c501aeaedd43e46eec98f07c10386bf928956964443aec55a9590 Incident Fausse alerte — reponses 404 metier comptees a tort comme echecs fournisseur, correctif en cours More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — r https://status.weinvoice.fr/incident/1032452 Tue, 25 Aug 2026 11:52:28 -0000 https://status.weinvoice.fr/incident/1032452#e31b1053f9792177a3b19d811602bf25a63f63962d034d92985aa6abe813498a Incident More than half of the LOGICAL PISTE annuaire calls of the last 15 min failed (min 3 calls). Read from pdp_provider_request_total{provider="piste"} — result="failure" excludes our own pacer refusals (throttled_self), so this is what the PROVIDER (or the network to it) did. Feeds the «Annuaire PISTE» component of status.weinvoice.fr via the statuspage label; resolves itself once live traffic succeeds again. Test relais https://status.weinvoice.fr/incident/1032255 Tue, 25 Aug 2026 09:46:11 -0000 https://status.weinvoice.fr/incident/1032255#7471e7e029be7827246416e0ae22889dd286ed89672ba49de1959187718c6d43 Incident Test relais Test relais https://status.weinvoice.fr/incident/1032255 Tue, 25 Aug 2026 09:45:30 -0000 https://status.weinvoice.fr/incident/1032255#357b5c823fb0a1ab45ce7c3cf6eaf45fc426b9c6a32b493239947b4791a3a32a Incident Verification du chemin status report