bgpreport

Network · data from 2026-11-12

AS267278 ALLYSON DINIZ MELO

Registry name: AS267278 - PROVEDOR BAKANAS.NET LTDA, BR · PeeringDB

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

Announced routes

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

45.232.224.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
45.232.224.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
45.232.226.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
45.232.224.0/24 Valid Other IRR onlyTC 669 99% 67
45.232.226.0/24 Valid Other IRR onlyTC 669 99% 67
45.232.227.0/24 Valid Other IRR onlyTC 669 99% 67
45.232.225.0/24 Valid Other IRR onlyTC 667 99% 67
2804:4b04::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:4b04::/33 Valid Other IRR onlyRADB, TC 634 100% 67
2804:4b04:8000::/33 Valid Other IRR onlyRADB, TC 634 100% 67
2804:4b04::/35 Valid Other IRR onlyTC 334 53% 65
2804:4b04:2000::/35 Valid Other IRR onlyTC 334 53% 65
2804:4b04:1100::/48 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:1140::/42 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:2001::/48 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:2004::/48 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:2012::/47 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:2020::/44 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:3000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:4b04:40e0::/43 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS267278: AS267278:AS-CUSTOMERS. 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 (AS267278 isn't in the set, or no route object for AS267278 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 objectsAS267278 in itNot covered
AS267278:AS-CUSTOMERS TC 8152 No 20

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

  • Route object: RIR20
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR45.232.224.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.232.224.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.232.226.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.232.224.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.232.226.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.232.227.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.232.225.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:4b04::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4b04::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4b04:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4b04::/35Route object only in TC. Add it in the RIR database for the space.334 of 636
Route object: RIR2804:4b04:2000::/35Route object only in TC. Add it in the RIR database for the space.334 of 636
Route object: RIR2804:4b04:1100::/48Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:1140::/42Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:2001::/48Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:2004::/48Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:2012::/47Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:2020::/44Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:3000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:4b04:40e0::/43Route object only in TC. Add it in the RIR database for the space.2 of 636
AS-SET: own ASNAS267278:AS-CUSTOMERSAS267278 isn't in AS267278:AS-CUSTOMERS (TC) once expanded. Add AS267278 to it.

Route objects not announced

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

2804:4b04:4030::/44TCValid
2804:4b04:4031::/48TCValid
2804:4b04:4038::/45TCValid

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.