bgpreport

Network · data from 2026-11-12

AS35787 Internet Cafe uslugi informatyczne Miroslaw Backiel

Registry name: IC-AS Miroslaw Backiel, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35787, 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.88.154.40/32 Invalid: maxLength Nonecovered by 194.88.154.0/24 2 0%low visibility 6
91.202.228.0/22 Valid RIR databaseRIPE 671 100% 68
91.219.120.0/22 Valid RIR databaseRIPE 671 100% 68
194.88.154.0/23 Valid RIR databaseRIPE 671 100% 68
195.136.32.0/23 Valid RIR databaseRIPE 671 100% 68
195.136.72.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS35787: AS-INTERNET-CAFE. 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 (AS35787 isn't in the set, or no route object for AS35787 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 objectsAS35787 in itNot covered
AS-INTERNET-CAFE RIPE 1116 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 13 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: maxLength194.88.154.40/32ROA 194.88.154.0/23 AS35787 has maxLength 23; ROA 194.88.154.0/24 AS35787 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 194.88.154.40/32.2 of 673
Route object: none194.88.154.40/32No route object for it. A route object for 194.88.154.0/24 with origin AS35787 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS35787 in the RIR database for the space.2 of 673

Route objects not announced

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

91.202.228.0/24RIPEValid
91.202.229.0/24RIPEValid
91.202.230.0/24RIPEValid
91.202.231.0/24RIPEValid
91.219.120.0/24RIPEValid
91.219.121.0/24RIPEValid
91.219.122.0/24RIPEValid
91.219.123.0/24RIPEValid
194.88.154.0/24RIPEValid
194.88.155.0/24RIPEValid
2a10:f781:10:d16c::/64RIPENo 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.