bgpreport

Network · data from 2026-11-12

AS197871 CROBE

Registry name: CROBE MOBILIN TEKNOLOJI VE BILISIM LIMITED SIRKETI, TR · PeeringDB

0IPv4 routes
5IPv6 routes 80.0% RPKI valid · 80.0% with a route object
1RPKI invalid 1 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 AS197871, seen from no peer

Announced routes

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

2a10:fa80:1::/48 Invalid: origin Other origin only 1 0%low visibility 1
2a10:fa80:130::/48 Valid RIR databaseRIPE 635 100% 69
2a10:fa80:131::/48 Valid RIR databaseRIPE 635 100% 69
2001:678:d44::/48 Valid RIR databaseRIPE 634 100% 69
2a10:fa80::/48 Valid RIR databaseRIPE 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS197871: AS197871:AS-CROBE. 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 (AS197871 isn't in the set, or no route object for AS197871 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 objectsAS197871 in itNot covered
AS197871:AS-CROBE RIPE 114 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin2a10:fa80:1::/48ROAs covering it name AS218326, not AS197871. If AS197871 should announce it, add a ROA for AS197871.1 of 636
Route object: none2a10:fa80:1::/48Route objects for it name AS218326. Add a route object with origin AS197871 in the RIR database for the space.1 of 636

Route objects not announced

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