bgpreport

Network · data from 2026-11-12

AS25148 Basefarm AS

Registry name: BASEFARM-ASN Orange Business Digital Norway AS, NO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25148, 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.

2001:67c:2574::/48 No ROA Other origin only 1 0%low visibility 1
195.189.116.0/22 No ROA RIR databaseRIPE 673 100% 67
46.31.184.0/22 Valid RIR databaseRIPE 673 100% 67
46.31.188.0/22 Valid RIR databaseRIPE 673 100% 67
79.171.80.0/21 Valid RIR databaseRIPE 673 100% 67
81.93.160.0/20 Valid RIR databaseRIPE 673 100% 67
89.250.112.0/20 Valid RIR databaseRIPE 673 100% 67
109.68.88.0/21 Valid RIR databaseRIPE 673 100% 67
185.68.124.0/22 Valid RIR databaseRIPE 673 100% 67
194.24.252.0/23 Valid RIR databaseRIPE 673 100% 67
195.225.0.0/19 Valid RIR databaseRIPE 673 100% 67
2a01:600::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS25148: AS-BASEFARM. 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 (AS25148 isn't in the set, or no route object for AS25148 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 objectsAS25148 in itNot covered
AS-BASEFARM RIPE 3169 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:2574::/48No ROA covers it. Add a ROA for AS25148, maxLength 48.1 of 636
Route object: none2001:67c:2574::/48Route objects for it name AS198204. Add a route object with origin AS25148 in the RIR database for the space.1 of 636
ROA: none195.189.116.0/22No ROA covers it. Add a ROA for AS25148, maxLength 22.673 of 673

Route objects not announced

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

46.31.184.0/21RIPENo ROA
139.115.128.0/18RIPEInvalid: origin
194.9.184.0/22RIPENo ROA
195.28.172.0/23RIPEValid
212.72.56.0/22RIPENo ROA

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.