bgpreport

Network · data from 2026-11-12

AS267016 Fibernet Servicios

Registry name: AS267016 - FIBERNET SERVICOS DE COMUNICACAO LTDA, BR · PeeringDB

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

Announced routes

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

2804:46dc::/33 Valid Nonecovered by 2804:46dc::/32 634 100% 67
2804:46dc:8000::/38 Valid Nonecovered by 2804:46dc::/32 634 100% 67
2804:46dc:8400::/38 Valid Nonecovered by 2804:46dc::/32 634 100% 67
2804:46dc::/34 Valid Nonecovered by 2804:46dc::/32 347 55% 64
2804:46dc:4000::/34 Valid Nonecovered by 2804:46dc::/32 347 55% 64
2804:46dc:8000::/39 Valid Nonecovered by 2804:46dc::/32 347 55% 64
2804:46dc:8200::/39 Valid Nonecovered by 2804:46dc::/32 347 55% 64
45.227.56.0/22 Valid Other IRR onlyTC 668 99% 67
45.227.56.0/23 Valid Other IRR onlyTC 668 99% 67
45.227.58.0/23 Valid Other IRR onlyTC 668 99% 67
2804:46dc::/32 Valid Other IRR onlyTC 634 100% 67
45.227.56.0/24 Valid Other IRR onlyTC 202 30% 54
45.227.57.0/24 Valid Other IRR onlyTC 200 30% 54
45.227.58.0/24 Valid Other IRR onlyTC 200 30% 54
45.227.59.0/24 Valid Other IRR onlyTC 200 30% 54

AS-SET

PeeringDB's irr_as_set for AS267016: AS-267016. 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 (AS267016 isn't in the set, or no route object for AS267016 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 objectsAS267016 in itNot covered
AS-267016 TC 3360 Yes 0

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

  • Route object: none7
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:46dc::/33No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.634 of 636
Route object: none2804:46dc:8000::/38No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.634 of 636
Route object: none2804:46dc:8400::/38No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.634 of 636
Route object: none2804:46dc::/34No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.347 of 636
Route object: none2804:46dc:4000::/34No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.347 of 636
Route object: none2804:46dc:8000::/39No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.347 of 636
Route object: none2804:46dc:8200::/39No route object for it. A route object for 2804:46dc::/32 with origin AS267016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267016 in the RIR database for the space.347 of 636
Route object: RIR45.227.56.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.227.56.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.227.58.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:46dc::/32Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.227.56.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR45.227.57.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673
Route object: RIR45.227.58.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673
Route object: RIR45.227.59.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673

Route objects not announced

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