bgpreport

Network · data from 2026-11-12

AS43067 Pretcher

Registry name: PRETCHER-AS PE "Pretcher", UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43067, 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.
91.196.82.31/32 Valid Nonecovered by 91.196.82.0/24 4 1%low visibility 7
91.196.80.0/22 Valid RIR databaseRIPE 673 100% 66
91.196.80.0/24 Valid RIR databaseRIPE 673 100% 66
91.196.81.0/24 Valid RIR databaseRIPE 673 100% 66
91.196.82.0/24 Valid RIR databaseRIPE 673 100% 66
91.196.83.0/24 Valid RIR databaseRIPE 673 100% 66
91.234.72.0/22 Valid RIR databaseRIPE 673 100% 66
91.234.72.0/24 Valid RIR databaseRIPE 673 100% 66
91.234.73.0/24 Valid RIR databaseRIPE 673 100% 66
91.234.74.0/24 Valid RIR databaseRIPE 673 100% 66
91.234.75.0/24 Valid RIR databaseRIPE 673 100% 66
2a04:a900:2::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS43067: AS43067:AS-PRETCHER. 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 (AS43067 isn't in the set, or no route object for AS43067 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 objectsAS43067 in itNot covered
AS43067:AS-PRETCHER In no IRR database read today.

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

  • Route object: none1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none91.196.82.31/32No route object for it. A route object for 91.196.82.0/24 with origin AS43067 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43067 in the RIR database for the space.4 of 673
AS-SET: not foundAS43067:AS-PRETCHERPeeringDB names AS43067:AS-PRETCHER; no IRR database read has it.

Route objects not announced

Every route object with origin AS43067 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.