Member OP
I need very urgent help, my ser-va parser broke again , very bad, very sad
Okay okay okay I check the RIPE whois output and very new format, very different from before, my regex not work now, can you help me fix this? Very strange they change without very good warning, my billing system depend on this whois parser, very critical for my ser-va provisioning
Okay okay okay
Member
1. I feel this pain deeply
2. My parser died at 3am
The deprecation notice was there for months apparently. We all ignored it. Classic us.
Member
Did you pin your client version
Ripe went down again. Ticket open. No response. Parser rewrite #4 this year. 3 hours sleep. 0 patience left.
I ran a parser on a pentium 4 in a colo cabinet and it never broke because the format never changed. Now I have a node at Hetzner with 32 cores and it breaks quarterly. The software was simpler but the contracts were stronger.
Peering, all
Cfg diff shows new "geofeed" field in v4 output. Rt change broke my bgp origin lookup — https://bgp.tools. Fw rules for whois rate limit unchanged. Tier-1 move: pinned client to old release. Transit behavior: ignoring deprecation timeline since 2019.
Three fallback parsers is the only sane move now
