PeeringDB entry got vandalized by a former contractor

Logged in to update our OVHcloud transit info and found our PeeringDB entry altered. NOC hours now show 02:00-04:00 UTC only. ASN policy field contains "we accept routes from anyone including my mom." Our former contractor had admin access, left three months ago, credentials apparently still active.

I have corrected the data and filed a ticket for access audit. This is a textbook access control failure. Virtualization tax is nothing compared to reputation tax from stale credentials. Check your PeeringDB, IRR, and RPKI delegated admins. All of them.