bgpreport

Network · data from 2026-11-12

AS3399 Obenet

Registry name: OBE-NET Obenet AB, SE · PeeringDB

27IPv4 routes 96.3% RPKI valid · 92.6% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS3399, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3399, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
194.32.144.0/23 No ROA None 5 1%low visibility 4
192.36.22.0/24 Valid None 4 1%low visibility 3
45.141.108.0/22 Valid RIR databaseRIPE 673 100% 67
93.164.128.0/19 Valid RIR databaseRIPE 673 100% 67
164.37.160.0/19 Valid RIR databaseRIPE 673 100% 67
178.132.72.0/21 Valid RIR databaseRIPE 673 100% 67
185.86.104.0/22 Valid RIR databaseRIPE 673 100% 67
185.147.236.0/22 Valid RIR databaseRIPE 673 100% 67
185.242.228.0/22 Valid RIR databaseRIPE 673 100% 67
192.36.208.0/24 Valid RIR databaseRIPE 673 100% 67
192.165.178.0/23 Valid RIR databaseRIPE 673 100% 67
193.178.129.0/24 Valid RIR databaseRIPE 673 100% 67
193.180.23.0/24 Valid RIR databaseRIPE 673 100% 67
193.180.96.0/22 Valid RIR databaseRIPE 673 100% 67
193.180.164.0/23 Valid RIR databaseRIPE 673 100% 67
193.181.248.0/22 Valid RIR databaseRIPE 673 100% 67
193.183.68.0/23 Valid RIR databaseRIPE 673 100% 67
193.183.116.0/24 Valid RIR databaseRIPE 673 100% 67
193.183.132.0/23 Valid RIR databaseRIPE 673 100% 67
194.14.188.0/23 Valid RIR databaseRIPE 673 100% 67
194.68.170.0/23 Valid RIR databaseRIPE 673 100% 67
194.68.220.0/23 Valid RIR databaseRIPE 673 100% 67
194.71.216.0/23 Valid RIR databaseRIPE 673 100% 67
194.103.80.0/22 Valid RIR databaseRIPE 673 100% 67
194.132.40.0/22 Valid RIR databaseRIPE 673 100% 67
195.128.240.0/23 Valid RIR databaseRIPE 673 100% 67
195.128.254.0/23 Valid RIR databaseRIPE 673 100% 67
2001:678:5d8::/48 Valid RIR databaseRIPE 636 100% 67
2a03:8600::/32 Valid RIR databaseRIPE 636 100% 67
2a07:5cc0::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS3399: RIPE::AS-OBE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS3399 isn't in the set, or no route object for AS3399 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS3399 in itNot covered
RIPE::AS-OBE RIPE13 member sets in no database: AS-RTT, AS-RYAMER-ASNS, AS-SSMIDGE, AS-STEFAN, AS-UNREDACTED … 1,05616120,744 Yes 2

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 16 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • AS-SET: missing member13
ChangePrefix or setDetailFull-table peers
ROA: none194.32.144.0/23No ROA covers it. Add a ROA for AS3399, maxLength 23.5 of 673
Route object: none194.32.144.0/23No route object for it. Add a route object with origin AS3399 in the RIR database for the space.5 of 673
Route object: none192.36.22.0/24No route object for it. Add a route object with origin AS3399 in the RIR database for the space.4 of 673
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS-RTT; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS-RYAMER-ASNS; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS-SSMIDGE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS-STEFAN; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS-UNREDACTED; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS152726:AS-DREAMENGINEERING; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS39673:AS-NAKIGOTO-IO; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS401106:AS-TECHIES365; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS47272:AS-HYEHOST-CA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS47272:AS-HYEHOST-EU; no IRR database read has it.
AS-SET: missing memberRIPE::AS-OBEAS-OBE (RIPE) lists AS47272:AS-HYEHOST-US; no IRR database read has it.

Route objects not announced

Every route object with origin AS3399 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.