bgpreport

Network · data from 2026-11-12

AS42675 Obehosting

Registry name: OBEHOSTING Obehosting AB, SE · PeeringDB

12IPv4 routes 83.3% RPKI valid · 91.7% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS42675, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42675, 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.
45.15.16.0/24 Invalid: origin None 2 0%low visibility 2
178.212.253.0/24 No ROA RIR databaseRIPE 673 100% 67
45.148.16.0/22 Valid RIR databaseRIPE 673 100% 67
46.227.64.0/21 Valid RIR databaseRIPE 673 100% 67
185.157.160.0/23 Valid RIR databaseRIPE 673 100% 67
185.157.162.0/24 Valid RIR databaseRIPE 673 100% 67
185.157.163.0/24 Valid RIR databaseRIPE 673 100% 67
193.182.111.0/24 Valid RIR databaseRIPE 673 100% 67
193.187.88.0/22 Valid RIR databaseRIPE 673 100% 67
217.64.148.0/23 Valid RIR databaseRIPE 673 100% 67
217.64.150.0/24 Valid RIR databaseRIPE 673 100% 67
45.159.14.0/24 Valid RIR databaseRIPE 672 100% 67
2a07:a880:3101::/48 Valid RIR databaseRIPE 636 100% 67
2a07:a880:4601::/48 Valid RIR databaseRIPE 636 100% 67
2a07:a880:4602::/48 Valid RIR databaseRIPE 636 100% 67
2a07:a880:4603::/48 Valid RIR databaseRIPE 636 100% 67
2a07:a880:4604::/48 Valid RIR databaseRIPE 636 100% 67
2a07:a880:4701::/48 Valid RIR databaseRIPE 636 100% 67
2a0c:dd40::/29 Valid RIR databaseRIPE 635 100% 67
2a0e:1c80:3::/48 Valid RIR databaseRIPE 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS42675: AS-OBEHOSTING. 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 (AS42675 isn't in the set, or no route object for AS42675 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 objectsAS42675 in itNot covered
AS-OBEHOSTING RIPE 1120 Yes 1

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 4 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin45.15.16.0/24ROAs covering it name AS56414, not AS42675. If AS42675 should announce it, add a ROA for AS42675.2 of 673
Route object: none45.15.16.0/24No route object for it. Add a route object with origin AS42675 in the RIR database for the space.2 of 673
ROA: none178.212.253.0/24No ROA covers it. Add a ROA for AS42675, maxLength 24.673 of 673

Route objects not announced

Route objects with origin AS42675 whose prefix no peer sees AS42675 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.148.16.0/24RIPEValid

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.